WO2020063317A1 - 一种通信方法及装置 - Google Patents
一种通信方法及装置 Download PDFInfo
- Publication number
- WO2020063317A1 WO2020063317A1 PCT/CN2019/104968 CN2019104968W WO2020063317A1 WO 2020063317 A1 WO2020063317 A1 WO 2020063317A1 CN 2019104968 W CN2019104968 W CN 2019104968W WO 2020063317 A1 WO2020063317 A1 WO 2020063317A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network
- entity
- pdu session
- information
- amf
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0027—Control or signalling for completing the hand-off for data sessions of end-to-end connection for a plurality of data sessions of end-to-end connections, e.g. multi-call or multi-bearer end-to-end data connections
-
- 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
-
- 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
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/18—Selecting a network or a communication service
-
- 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
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/15—Setup of multiple wireless link connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/24—Interfaces between hierarchically similar devices between backbone network devices
Definitions
- the present application relates to the field of communication technologies, and in particular, to a communication method and device.
- the public network operator strongly requires that private network users open an account on the public network, that is, the unified data management (UDM) entity of the public network Perform contract management.
- UDM unified data management
- a public network and private network interworking architecture is defined in the prior art: an enterprise private network and an operator's public network are interconnected on the core network; at the same time, in order to protect the security of both parties, both parties can use a unified agent ( proxy) server as a routing node.
- proxy unified agent
- a communication method and apparatus are provided.
- the method is applicable to a terminal device, and includes: the terminal device generates a first message, where the first message is used to request establishment of a home route to a protocol data unit PDU in a first network; A session; the terminal device sends the first message to a first access and mobility management function AMF entity, where the first AMF entity is a network element in a second network.
- the second network when the terminal device is located in the service range of the second network, the second network can send a request through the RAN node of the second network to establish a PDU session with the home route to the first network.
- the terminal device can implement the application Data services provided by the first network.
- the second network may be a private network
- the first network may be a public network
- the second network may be a public network
- the first network may be a private network.
- the first message includes first indication information, and the first indication information is used to indicate that the PDU session is a PDU session that is home-routed to the first network.
- the first indication information includes at least one of a data network name, slice selection information, network type indication information, or identification information of the first network.
- the first AMF entity may determine that the PDU session requested by the terminal device is a local route or a home route, which may also be referred to as Allow local routing.
- the first message includes at least one of a data network name or slice selection information.
- the first message does not include the first indication information, and only includes the data network name or slice selection information.
- the first AMF entity may determine the terminal device.
- the PDU session requested to be established is a local route or a home route. Compared with the scheme of adding the first indication information in the first message, the signaling overhead can be saved.
- a communication method is provided.
- the method is applicable to a first AMF entity, and includes: a first access and mobility management function AMF entity receiving a first message from a terminal device, the first message used for requesting Establishing a protocol data unit PDU session that is home routed to the first network; the first AMF entity sends a second message to a first session management function SMF entity according to the first message, the second message being used to request the Core network tunnel information for a PDU session; the first AMF entity receives first core network tunnel information from the first SMF entity, and sends the first core network tunnel information to a second AMF entity, the first AMF entity
- the core network tunnel information is used to establish a data channel for the PDU session between a first user plane function UPF entity and the UPF entity in the first network; wherein the first AMF entity, the first SMF entity, and The first user plane function UPF entity is a network element in a second network, and the second AMF entity is a network element in the first network.
- the terminal device requests the AMF entity in the second network to establish a PDU session routed to the first network, and the AMF entity in the second network requests the first core of the PDU session to the SMF entity in the second network according to the request.
- Network tunnel information and send the first core network tunnel information to the AMF entity in the first network, and the AMF entity in the first network sends the first core network tunnel information to the first network through the SMF entity in the first network And obtains the second core network tunnel information of the PDU session from the UPF entity in the first network, and further sends the second core network tunnel information to the first network through the AMF entity and the SMF entity in the second network.
- the UPF entity in the two networks has successfully established a PDU session between the UPF entity in the first network and the UPF entity in the second network, that is, the two PDU sessions between UPF entities in this network, thereby solving the communication problem between public and private networks.
- the first message includes first indication information, and the first indication information is used to indicate that the PDU session is a PDU session that is home-routed to the first network.
- the first indication information includes at least one of a data network name, slice selection information, network type indication information, or identification information of the first network.
- the second message includes the first indication information.
- the first message includes data network name and / or slice selection information
- the method further includes: the first AMF entity selecting information and indication information according to the data network name and / or slice.
- the first AMF entity selecting information and indication information according to the data network name and / or slice.
- determining indication information corresponding to the data network name and / or slice selection information in the first message when the indication information corresponding to the data network name and / or slice selection information in the first message is used to indicate
- the first AMF entity determines that the home network of the PDU session is the first network according to the identity of the terminal device, or the first AMF entity
- the correspondence between the data network name and / or slice selection information included in the subscription information of the terminal device and the home routing network identifier determines that the home network of the PDU session is the first network.
- the first AMF entity can specifically determine the network for which the PDU session requires a home route.
- the second message includes second indication information; wherein when the first network is a private network and the second network is a public network, the second indication information is used Indicating that the type of the PDU session requested to be established is a private network type; or when the first network is a public network and the second network is a private network, the second indication information is used to indicate the request The type of the established PDU session is the public network type.
- the method further includes: the first AMF entity selects a second SMF entity, and the second SMF entity is located in the first network.
- the second message includes an identifier of the second SMF entity; and when the first network is a private network, the identifier of the second SMF entity is used to indicate all The second SMF entity is an SMF entity in a private network; or when the first network is a public network, the identifier of the second SMF entity is used to indicate that the second SMF entity is an SMF entity in a public network .
- the method further includes: the first AMF entity sending slice selection information, a data network name, a PDU session establishment request, or identification information of the second network to the second AMF entity At least one of.
- the method further includes that the first AMF entity receives second core network tunnel information from the second AMF entity, and the second core network tunnel information is used to establish the A PDU session is a data channel between the first UPF entity and a second UPF entity in the first network; the first AMF entity sends the second core network tunnel information to the first SMF entity.
- the method further includes: the first AMF entity receives quality of service QoS parameter information of the PDU session from the second AMF entity; the first AMF entity sends the The first SMF entity sends the QoS parameter information of the PDU session; the first AMF entity receives the QoS configuration file and the QoS rule from the first SMF entity; the first AMF entity sends all the information to the radio access network device The QoS configuration file; the first AMF entity sends the QoS rule to a terminal device.
- the second message is a context request for creating a PDU session; the first core network tunnel information is carried in the context response for creating a PDU session, or the first core network tunnel The information is carried in the N16 'message transmission request.
- a communication method is provided.
- the communication method is applied to a first SMF entity and may include: a first session management function SMF entity receiving a second message from a first access and mobility management function AMF entity;
- the second message is used to request core network tunnel information for a protocol data unit PDU session;
- the first SMF entity sends a first core network tunnel message to the first AMF entity according to the second message, and the first core
- the network tunnel information is used to establish a data channel of the PDU session between the first user plane function UPF entity and the UPF entity in the first network; wherein the first AMF entity, the first SMF entity, and the first A UPF entity is a network element in the second network.
- the second message includes first indication information; wherein when the first network is a private network, the second indication information is used to indicate the PDU session requested to be established The type of the private network is a private network type; or when the first network is a public network, the second indication information is used to indicate that the type of the PDU session requested to be established is a public network type.
- the second message includes the second indication information, and the second indication information is used to indicate that a type of the PDU session is a private network type or a public network type.
- the second message includes an identifier of the second SMF entity; and when the first network is a private network, the identifier of the second SMF entity is used to indicate all The second SMF entity is an SMF entity in a private network; when the first network is a public network, the identifier of the second SMF entity is used to indicate that the second SMF entity is an SMF entity in a public network.
- the method further includes: the first SMF entity determines the first UPF entity according to the first instruction information or the second instruction information; the first SMF entity Assigning the first core network tunnel information to the first UPF entity; the first SMF entity sending the first core network tunnel information to the first UPF entity.
- the method further includes: the first SMF entity receives second core network tunnel information from the first AMF entity, and the second core network tunnel information is used to establish the A PDU session is a data channel between the first UPF entity and a second UPF entity in the first network; the first SMF entity sends the second core network tunnel information to the first UPF entity.
- the method further includes: the first SMF entity receives QoS parameter information from the first AMF entity; the first SMF entity obtains the QoS parameter information according to the QoS parameter information A QoS configuration file and a QoS rule of a PDU session; the first SMF entity sends the QoS configuration file and the QoS rule to the first AMF entity.
- the second message is a context request for creating a PDU session; the first core network tunnel message is carried in the context response for creating a PDU session, or the first core network tunnel The information is carried in the N16 'message transmission request.
- a communication method is provided.
- the communication method is applicable to a second AMF entity, and includes: a second access and mobility management function AMF entity receiving first core network tunnel information from a first AMF entity, said The first core network tunnel information is used to establish a data channel for a protocol data unit PDU session between a first user plane function UPF entity and a UPF entity in the first network; the second AMF entity sends all data to the second session management function SMF entity.
- the first core network tunnel information wherein the second AMF entity and the second SMF entity are network elements in the first network, and the first AMF entity and the first UPF entity are second Network elements in the network.
- the method further includes: the second AMF entity sends third instruction information to the second SMF entity, the third instruction information is used to indicate that the PDU session is a slave session.
- the third indication information includes identification information of the second network.
- the method further includes: the second AMF entity receiving second core network tunnel information from the second SMF entity, the second core network tunnel information being used to establish the A PDU session is a data channel between the first UPF entity and a second UPF entity in the first network; the second AMF entity sends the second core network tunnel information to the first AMF entity.
- the method further includes: the second AMF entity receives QoS parameter information of the PDU session from the second SMF entity; the second AMF entity sends the first AMF entity to the first The AMF entity sends QoS parameter information of the PDU session.
- the second message is a context request for creating a PDU session; the first core network tunnel information is carried in the context response for creating a PDU session, or the first core network tunnel The information is carried in the N16 'message transmission request.
- the first core network tunnel information is carried in a context request for creating a PDU session
- the second core network tunnel information is carried in a context response for creating a PDU session, or the second core network tunnel information is carried in an N16 'message transmission request.
- a communication method is provided.
- the communication method is applicable to a second SMF entity, and includes: a second session management function SMF entity receiving first core network tunnel information from a second access and mobility management function AMF entity
- the first core network tunnel information is used to establish a data channel between a protocol data unit PDU session between a first user plane function UPF entity and a UPF entity in the first network; the second SMF entity reports to the second AMF
- the entity sends second core network tunnel information, and the second core network tunnel information is used to establish a data channel of the PDU session between the first UPF entity and the second UPF entity; wherein the first UPF entity Are network elements in a second network, and the second AMF entity, the second SMF entity, and the second UPF entity are network elements in the first network.
- the method further includes: the second SMF entity receives third indication information from the second AMF entity; wherein the third indication information is used to indicate the PDU session Is a PDU session routed from the second network home to the first network.
- the third indication information includes identification information of the second network.
- the method further includes: the second SMF entity determines the second UPF entity according to the third instruction information; the second SMF entity is the second UPF entity Allocating the second core network tunnel information; the second SMF entity sending the second core network tunnel information to the second UPF entity.
- the method further includes: the second SMF entity sending QoS parameter information to the second AMF entity.
- the first core network tunnel information is carried in a context request for creating a PDU session
- the second core network tunnel information is carried in a context response for creating a PDU session, or the second core network tunnel information is carried in a N16 'message transmission request.
- a communication device has a function of implementing the behavior of a terminal device in any of the first aspect and the first possible design of the first aspect.
- the functions may be implemented by hardware, and may also be implemented by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the functions described above.
- the device may be a chip or an integrated circuit.
- the device includes a memory and a processor.
- the memory stores a set of programs.
- the processor is configured to execute the programs stored in the memory.
- the device may execute the first aspect and the first aspect. The method described in any possible design.
- the device further includes a transceiver for communication between the device and other network elements.
- the device is a terminal device.
- a communication device has a function of implementing the behavior of the first AMF entity in any one of the second aspect and the second possible design of the second aspect.
- the functions may be implemented by hardware, and may also be implemented by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the functions described above.
- the device may be a chip or an integrated circuit.
- the device includes a memory and a processor.
- the memory stores a set of programs.
- the processor is configured to execute the programs stored in the memory.
- the device may execute the second aspect and the second aspect. The method described in any possible design.
- the device further includes a transceiver for communication between the device and other network elements.
- the device is a first AMF entity.
- a communication device has a function of realizing the behavior of the first SMF entity in any of the third aspect and the possible design of the third aspect.
- the functions may be implemented by hardware, and may also be implemented by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the functions described above.
- the device may be a chip or an integrated circuit.
- the device includes a memory and a processor.
- the memory stores a set of programs.
- the processor is configured to execute the programs stored in the memory.
- the device may execute the third aspect and the third aspect. The method described in any possible design.
- the device further includes a transceiver for communication between the device and other network elements.
- the device is a first SMF entity.
- a communication device in a ninth aspect, has a function of implementing the behavior of the second AMF entity in any one of the foregoing fourth aspect and the fourth possible design.
- the functions may be implemented by hardware, and may also be implemented by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the functions described above.
- the device may be a chip or an integrated circuit.
- the device includes a memory and a processor.
- the memory stores a set of programs.
- the processor is configured to execute the programs stored in the memory.
- the device may execute the fourth aspect and the fourth aspect. The method described in any possible design.
- the device further includes a transceiver for communication between the device and other network elements.
- the device is a second AMF entity.
- a communication device has a function of implementing the behavior of the second SMF entity in any one of the foregoing fifth aspect and the fifth possible design.
- the functions may be implemented by hardware, and may also be implemented by hardware executing corresponding software.
- the hardware or software includes one or more modules corresponding to the functions described above.
- the device may be a chip or an integrated circuit.
- the device includes a memory and a processor.
- the memory stores a set of programs.
- the processor is configured to execute the programs stored in the memory.
- the device may execute the fifth aspect and the fifth aspect. The method described in any possible design.
- the device further includes a transceiver for communication between the device and other network elements.
- the device is a second SMF entity.
- a chip is provided, the chip is connected to a memory or the chip includes a memory for reading and executing a software program stored in the memory, so as to implement any of the foregoing aspects and any possible aspect The method described in the design.
- a communication system includes the device described in any two of the first to fifth aspects or any two or more aspects.
- a computer storage medium storing a computer program, the computer program including instructions for performing the foregoing aspects and any possible design method in each aspect.
- a computer program product that, when a computer reads and executes the computer program product, causes the computer to perform the methods described in the above aspects and any possible design of each aspect.
- 1A and 1B are network architectures provided by embodiments of the present application.
- FIG. 2 is a schematic flowchart of a communication method according to an embodiment of the present application.
- FIG. 3 is a schematic flowchart of a communication method according to an embodiment of the present application.
- FIG. 4 is a schematic flowchart of a communication method according to an embodiment of the present application.
- FIG. 5 is a schematic flowchart of a communication method according to an embodiment of the present application.
- FIG. 6 is a schematic flowchart of a communication method according to an embodiment of the present application.
- FIG. 7 is a schematic flowchart of a communication method according to an embodiment of the present application.
- FIG. 8 is a schematic flowchart of a communication method according to an embodiment of the present application.
- FIG. 9 is a schematic flowchart of a communication method according to an embodiment of the present application.
- FIG. 10 is a schematic structural diagram of a communication device according to an embodiment of the present application.
- FIG. 11 is a schematic structural diagram of a communication device according to an embodiment of the present application.
- FIG. 12 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
- a terminal device is a device that provides voice and / or data connectivity to users. Specifically, it may be a user equipment (UE), a mobile station (MS), or a mobile terminal (MT). For example, a handheld device, a vehicle-mounted device, etc. having a wireless connection function.
- some examples of terminals are: mobile phones, tablet computers, laptops, handheld computers, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (augmented reality) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, and smart grids Wireless terminals in transportation, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes.
- a radio access network may be composed of one or more RAN nodes, such as a 5G-RAN node or a base station in a future evolved system.
- the RAN node can implement functions such as a wireless physical layer, resource scheduling, wireless resource management, wireless access control, and mobility management.
- a RAN node may be connected to a user plane function (UPF) entity through an N3 interface, and is used to transmit data of a terminal device.
- UPF user plane function
- a RAN node may be connected to an access and mobility management function (AMF) entity through an N2 interface, and is used to establish a control plane signaling connection and implement functions such as wireless access bearer control.
- AMF access and mobility management function
- Private network that is, a private network deployed by an enterprise in order to meet the needs of corporate privacy, communication security, user contract management, and exclusive use of network resources.
- the control plane of the private network may include an AMF entity and a session management function (SMF) entity.
- the user plane may include UPF entities.
- the private network may further include network elements such as a UDM entity, an authentication server function (AUSF) entity, and the like.
- the public network can be an operator network.
- the control plane may include AMF entities and SMF entities.
- the user plane may include UPF entities.
- the public network also includes a UDM entity, an AUSF entity, a policy control function (PCF) entity, a network slice selection function (NSSF) entity, and a network function library function (network function, NF ) Repository (function, NRF) entities and other network elements.
- PCF policy control function
- NRF network function library function
- the AMF entity is mainly responsible for mobility management and access management. For example, it is responsible for maintaining and managing terminal status information, responsible for terminal authentication, selecting network slices, or selecting SMF entities. Specifically, the AMF entity can be used to implement functions other than session management among mobility management (mobility management entity) entity functions in the 4G system.
- mobility management mobility management entity
- the SMF entity is mainly responsible for the control plane functions related to the session management of the terminal device, such as the selection of the UPF entity, the allocation of IP addresses, the QoS management of the session, and the acquisition of policy control and charging from the PCF entity. , PCC) strategy.
- the UPF entity as the anchor point of the PDU session connection, is mainly responsible for data packet filtering, data transmission / forwarding, rate control, and charging information generation of the terminal device.
- At least one or more of a, b, or c may represent: a; b; c; a and b; a and c; b and c; or a, b, and c.
- a, b, and c may be single or plural.
- the network architecture can be used to implement interconnection and interconnection between a private network of an enterprise and a public network of an operator.
- an AMF entity in a private network and an AMF entity in a public network can directly communicate.
- the UPF entity in the private network and the UPF entity in the public network can communicate directly.
- the AMF entity in the public network and the AMF entity in the private network can communicate through a CP proxy server.
- the UPF entity in the public network and the UPF entity in the private network can communicate through the UP proxy server.
- the terminal device can be home-routed from the private network to the public network.
- the terminal device can be connected to the private network AMF entity through the private network RAN node and through the private network.
- the AMF entity interacts with the public network AMF entity to establish a protocol data unit (PDU) session between the public and private networks.
- the PDU session includes at least a data channel between the private network UPF entity and the public network UPF entity.
- the terminal device can access the public network, so that the data services provided by the public network can be utilized.
- the terminal device can be routed from the public network to the private network. Specifically, the terminal device can access the public network AMF entity through the public network RAN node, and the private network AMF entity and the public network Network AMF entities interact to establish a PDU session between the public and private networks.
- the PDU session includes at least a data channel between the private network UPF entity and the public network UPF entity. Based on the PDU session, the terminal device can access the private network, thereby utilizing the data services provided by the private network.
- a terminal device may first register respectively to a public network and a private network, then establish a PDU session between the public and private networks, and finally use the PDU session to access a public network or a private network.
- the network architecture shown in FIG. 1A or FIG. 1B further includes a data network (DN), and the DN may be connected to a UPF entity in a public network and a UPF entity in a private network, respectively.
- DN data network
- FIG. 1A and FIG. 1B is only an example of an application network architecture of the method or device provided in this application, and is not intended to be limiting.
- an embodiment of the present application provides a communication method, which can be used to establish a PDU session between a first network and a second network.
- the first network may be a private network in the network architecture shown in FIG. 1B
- the second network may be a public network in the network architecture shown in FIG. 1B, or the first network may be a public network in the network architecture shown in FIG. 1A.
- Network the second network may be a private network in the network architecture shown in FIG. 1A.
- the second network may include a first AMF entity, a first SMF entity, and a first UPF entity
- the first network may include a second AMF entity, a second SMF entity, and a second UPF entity.
- the communication process may be specifically described as follows.
- S201 The terminal device generates a first message.
- the first message may be used to request the establishment of a PDU session with a home route to the first network, or be used to request to establish a PDU session carrying the first network data service.
- the first message may be an existing message, for example, an uplink non-access stratum transport (UL, NAS, or TRANSPORT) message; or a new message without limitation.
- UL uplink non-access stratum transport
- NAS NAS
- TRANSPORT TRANSPORT
- the first message is used to request establishment of a home route to a PDU session in the first network.
- the first message may include first indication information, and the first indication information may be used to indicate that the PDU session is a PDU session that is home-routed to the first network.
- the first message is used to request to establish a PDU session carrying a first network data service.
- the first message may include first indication information, and the first indication information may be used to indicate that the PDU session is a PDU session carrying a data service of the first network.
- the first indication information in the above two examples may include at least one of the following information: data network name (DNN), slice selection information, network type indication information, or identification information of the first network.
- DNN data network name
- slice selection information may include at least one of the following information: slice selection information, network type indication information, or identification information of the first network.
- the first indication information is used to instruct the establishment of a home route to a PDU session in the public network.
- the network type indication information may be specifically used to indicate the public network.
- the identification information of the first network may be specifically the identification information of the public network. .
- the public network identification information can be used to identify the public network.
- the public network identification information can be a public land mobile network identification (PLMN ID).
- PLMN ID can be a mobile country code (mobile country code (MCC) and mobile network code (MNC), a specific PLMN ID field is assigned to the public network, for example: China Mobile's PLMN is 46000, China Unicom's PLMN is 46001. Among them, 460 is MCC, 00/01 is MNC.
- the first indication information is used to instruct the establishment of a PDU session for home routing to the private network
- the network type indication information may be specifically used to indicate the private network
- the identification information of the first network may specifically be the identification information of the private network .
- the private network identification information can be used to identify the private network.
- the private network identification information can be a PLMN ID.
- the PLMN ID consists of an MCC and a private mobile network code (PMNC).
- the PLMN ID field is assigned to the private network.
- the PLMN ID of Sany Heavy Industry Network is 46056
- the PLMN ID of China Petroleum Enterprise Network is 46057, of which 460 is MCC and 56/57 is PMNC.
- the network identifier of an enterprise private network includes a private network indicator bit, which is used to indicate the private network.
- the private network identifier consists of MCC, private network indicator bit, and PMNC.
- the PLMN ID is 460156
- the PLMN ID of China Petroleum Enterprise Network is 460157, where 460 is MCC, 1 is the private network indicator bit, and 56/57 is PMNC.
- the slice selection information may be session management network slice selection auxiliary information (session management-network selection selection information, S-NSSAI).
- the first message may not include the first indication information.
- the first message may include at least one of a data network name or slice selection information, and the data network name or slice selection information may identify the first The internet.
- the first message includes a PDU session establishment request.
- the terminal device sends the first message to a first AMF entity.
- the first AMF entity sends a second message to the first SMF entity according to the first message.
- the second message may be used to request core network tunnel information of the PDU session, and the core network tunnel information is used to establish a data channel between the first UPF entity and the second UPF entity.
- the second message may be an existing message, for example, a context request for creating a PDU session, or a new message, without limitation.
- the first message includes data network name and / or slice selection information
- the first AMF entity may determine the type of the request for establishing a PDU session according to the data network name and / or slice selection information; and establish a PDU according to the request.
- the type of the session determines the second indication information; and generates a second message according to the second indication information.
- the second message may include second indication information.
- the second indication information is used to indicate that the type of the PDU session requested to be established is a private network; or when the first network is a private network;
- the second indication information is used to indicate that the type of the PDU session requested to be established is a public network.
- the first message may include first indication information.
- the first AMF entity may obtain the first indication information from the first message, and generate a second message based on the obtained first indication information.
- the second message may include the first indication information.
- the first message may include first indication information.
- the first AMF entity may obtain the first instruction information from the first message, generate the second instruction information based on the first instruction information, and generate the second instruction information based on the first instruction information and / or the second instruction information. Message.
- the second message may include the first indication information and / or the second indication information.
- the first AMF entity may determine the type of the requested PDU session according to the data network name, slice selection information, network type indication information, and / or identification information of the first network in the first indication information, and according to the PDU session, Type, determine the second instruction information.
- the first SMF entity sends the first core network tunnel information to the first AMF entity according to the second message.
- the first core network tunnel information may be used to establish a data channel of the PDU session between the first UPF entity and the UPF entity in the first network.
- the first core network tunnel information is core network tunnel information of the PDU session on the first UPF entity side.
- the second message includes the first indication information and / or the second indication information
- the first SMF entity determines the first UPF entity according to the first indication information or the second indication information, and allocates the first UPF entity.
- the first core network tunnel information sends the first core network tunnel information to the first AMF entity.
- the first SMF entity may determine the first UPF entity according to the first instruction information or the second instruction information in the following two implementation manners.
- the second indication information is used to indicate a type of requesting to establish a PDU session.
- the first SMF entity may determine the type of the request for establishing a PDU session according to the above-mentioned second instruction information, and based on the type of the request for establishing a PDU session, select the first UPF entity in the UPF entity resource pool of the second network to pass The first UPF entity implements communication between the first network and the second network. For example, if the second network is a public network and the first network is a private network, the first SMF entity may select a UPF entity from the public network's UPF entity resource pool, and further establish the selected UPF entity and the private network UPF entity. Connection for communication between private and public networks.
- the first message is used to request the establishment of a home route to a PDU session in the first network.
- the first SMF entity may determine the type of the PDU session according to the data network name, slice selection information, network type indication information, and / or identification information of the first network in the first instruction information, and establish a PDU conference based on the request.
- Type in the UPF entity resource pool of the second network, select the first UPF entity to implement communication between the first network and the second network.
- the first SMF entity may use an existing method (for example, random selection, or according to load selection) to select a UPF entity as the first UPF entity, and allocate first core network tunnel information to the first UPF entity To send the first core network tunnel information to the first AMF entity.
- an existing method for example, random selection, or according to load selection
- the first core network tunnel information may be allocated by the first SMF entity or the first UPF entity, and is not intended to limit the present application. If the first core network tunnel information is allocated by the first UPF entity, the first UPF entity sends the first core network tunnel information to the first SMF entity, and then the first SMF entity sends the first core network tunnel information to the first SMF entity through S204a. First AMF entity.
- the above method further includes: S204b: The first SMF entity sends the first core network tunnel information to the first UPF entity.
- S205 The first AMF entity sends the first core network tunnel information to the second AMF entity.
- the above method further includes: the first AMF entity sending at least one of slice selection information, a data network name, a PDU session establishment request, or identification information of the second network to the second AMF entity.
- the identification information of the second network is used to identify the second network to notify the second AMF entity of the network currently communicating with the second AMF entity.
- first core network tunnel information, slice selection information, data network name, PDU session establishment request, and identification information of the second network may be carried in the same message, or may be carried in different messages, respectively. This application is not limited.
- the second AMF entity sends the first core network tunnel information to the second SMF entity.
- the second SMF entity receives the second core network tunnel information from the second AMF entity.
- the above method further includes: the second AMF entity sends third instruction information to the second SMF entity, and accordingly, the second SMF entity receives the third instruction information from the second AMF entity.
- the third indication information may be used to indicate that the PDU session is a PDU session routed from the second network home route to the first network, or to indicate that the PDU session visits a public land mobile network, VPLMN) is a private network type or a public network type.
- the third indication information may include identification information of the second network.
- first core network tunnel information and the third indication information may be carried in the same message, or may be carried in different messages.
- the second SMF entity sends the second core network tunnel information to the second AMF entity.
- the second AMF entity receives the second core network tunnel information from the second SMF entity.
- the second core network tunnel information may be used to establish a data channel of the PDU session between the first UPF entity and the second UPF entity.
- the second core network tunnel information is core network tunnel information of the PDU session on the second UPF entity side.
- the second SMF entity may determine the second UPF entity according to the third instruction information, and the second SMF entity allocates a second to the second UPF entity. Core network tunnel information, and send the second core network tunnel information to the second AMF entity.
- the third indication information may be used to indicate that the PDU session is a PUD session that is routed from the private network to the public network, and the second SMF entity is obtaining After the third indication information, it can be determined that the current PDU session is not a local route, then a second UPF entity can be selected from the resource pool of the UPF entity, which is specifically used to communicate with the private network.
- the second SMF entity may use an existing method (for example, random selection, or according to load selection) to select a UPF entity as the second UPF entity, assign the second core network tunnel information to the second UPF entity, and Send the second core network tunnel information to the second AMF entity.
- an existing method for example, random selection, or according to load selection
- the above method further includes: S207b: The second SMF entity sends the first core network tunnel information to the second UPF entity, or the first core network tunnel information and the second core network tunnel information.
- the tunnel information of the second core network may be allocated by the second SMF entity or by the second UPF entity, which is not limited. If the second core network tunnel information is allocated by the second UPF entity, the second UPF entity sends the second core network tunnel information to the second SMF entity, and then the second SMF entity sends the second core network tunnel through S207a The information is sent to the second AMF entity. At this time, only the first core network tunnel information may be sent in S207b.
- the above method further includes: the second SMF entity sending QoS parameter information of the PDU session to the second AMF entity.
- the second AMF entity receives the QoS parameter information of the PDU session from the second SMF entity.
- the QOS parameter information may include QoS rules (QoS rules), QoS profiles (QoS profiles), and QoS flow granularity (QoS parameters).
- QoS rules QoS rules
- QoS profiles QoS profiles
- QoS flow granularity QoS parameters
- tunnel information and QoS parameter information of the second core network may be carried in the same message, or may be carried in different messages, without limitation.
- the second AMF entity sends the second core network tunnel information to the first AMF entity.
- the first AMF entity receives the second core network tunnel information from the second AMF entity.
- the above method further includes: the second AMF entity sending quality of service (QoS) parameter information of the PDU session to the first AMF entity.
- QoS quality of service
- the first AMF entity receives the QoS parameter information of the PDU session from the second AMF entity.
- the second core network tunnel information and QoS parameter information may be carried in the same message, or may be carried separately in different messages.
- the first AMF entity sends the second core network tunnel information to the first SMF entity.
- the first SMF entity receives the second core network tunnel information from the first AMF entity.
- the above method further includes: S210: The first SMF entity sends the second core network tunnel information to the first UPF entity.
- the method further includes: the first AMF entity sending the QoS parameter information of the PDU session to the first SMF entity.
- the first SMF entity receives the QoS parameter information from the first AMF entity.
- the first SMF entity may obtain a QoS configuration file and a QoS rule of the PDU session according to the QoS parameter information.
- the first SMF entity may send a QoS configuration file and a QoS rule to the first AMF entity.
- the first AMF entity receives the QoS configuration file and QoS rules from the first SMF entity, and then the first AMF entity can send the QoS profile to the RAN node, and the first AMF entity can send the QoS rule to the terminal device. .
- the QoS parameter information may include a QoS configuration file and a QoS rule.
- the first SMF entity may obtain a QoS configuration file and a QoS rule in the QoS parameter information.
- the second message in step S203 is specifically a context request for creating a PDU session, and the first core network tunnel information in step S204a is carried in a context response for creating a PDU session.
- the second message in step S203 is specifically a context request for creating a PDU session, and the first core network tunnel information in step S204a is carried in the N16 'message transmission request.
- the first core network tunnel information in step S206 is carried in a context request for creating a PDU session
- the second core network tunnel information in step S207a is carried in a context response for creating a PDU session.
- the first core network tunnel information in step S206 is carried in a context request for creating a PDU session
- the second core network tunnel information in step S207a is carried in a N16 'message transmission request.
- the above method further includes: the first AMF entity selecting a second SMF entity.
- the second message may include an identifier of the second SMF entity.
- the second SMF entity is an SMF entity in the private network.
- the identifier of the second SMF entity may be specifically an identifier of an SMF entity in the private network.
- the terminal device requests the AMF entity in the second network to establish a PDU session routed to the first network, and the AMF entity in the second network requests the PDU session to the SMF entity in the second network according to the request.
- the first core network tunnel information and send the first core network tunnel information to the AMF entity in the first network, and the AMF entity in the first network sends the first core network tunnel information through the SMF entity in the first network To the UPF entity in the first network, and obtain the second core network tunnel information of the PDU session from the UPF entity in the first network, and further pass the second core network tunnel information through the AMF entity and the SMF in the second network
- the entity sends to the UPF entity in the second network, and the PDU session is successfully established between the UPF entity in the first network and the UPF entity in the second network, that is, through the communication interface between the AMF entities in the two networks.
- the PDU session between the UPF entities in the two networks was successfully established, thereby solving the communication problem between the public network and the private network.
- the first message includes a data network name and / or slice selection information
- the foregoing method further includes:
- the first AMF entity determines, according to the correspondence between the data network name and / or slice selection information and the indication information, the indication information corresponding to the data network name and / or slice selection information in the first message;
- the first AMF entity determines the network to which the PDU session belongs.
- the above-mentioned correspondence relationship may be: a correspondence relationship between the data network name and the slice selection information as a combination and the indication information, or a correspondence relationship between the data network name and the indication information; or, between the slice selection information and the indication information Corresponding relationship.
- the corresponding relationship may be configured on the first AMF entity, or in the contract data of the terminal device.
- the first AMF entity may obtain the corresponding relationship in the contract data of the terminal device.
- the first AMF entity may obtain the subscription data of the terminal device from the UDM entity.
- the indication information is used to indicate whether the PDU session allows local routing. Specifically, different meanings can be adopted by setting different values. For example, the indication information is 1, which may indicate that the PDU session does not allow local breakout. The indication is 0, which indicates that the PDU session allows local routing.
- disallowing local routes can also be called home routes, specifically referring to the home network of the PDU session home route to the terminal device. Allowing local routing can also be called non-home routing, which specifically means that PDU sessions can be routed through the local network.
- the network in which the first AMF entity determines the home route of the PDU session may use the following methods:
- Method 1 The first AMF entity determines that the home network of the PDU session is the first network according to the identity of the terminal device.
- the identifier of the terminal device may include a public land mobile network (PLMN) identifier, and the PLMN identifier may identify an operator's public network to which the terminal device belongs.
- PLMN public land mobile network
- the first AMF entity may determine the public network of the operator of the home route according to the PLMN identity of the terminal device. For example, the network of a mobile operator, or the network of a China Unicom operator, or the network of a telecommunications operator.
- the first AMF entity determines the home network of the PDU session as the first network according to the correspondence between the data network name and / or slice selection information included in the subscription information of the terminal device and the home routing network identifier.
- the first AMF entity can determine that the PDU session requested by the terminal device to establish requires a home route.
- the first AMF entity can determine the core network tunnel information of the PDU session that the terminal device requests to establish on the side of the first UPF entity.
- the first AMF entity cannot determine the network to which the PDU session belongs.
- the first AMF entity can specifically determine the network to which the PDU session requires the home route.
- a PDU session between the terminal equipment access network and the terminal equipment home network.
- a PDU is established by accessing a communication interface between the SMF entity and the home SMF entity. Conversation.
- a communication interface is provided only between AMF entities of two networks, and a communication interface is not provided between SMF entities of the two networks.
- the method provided in the embodiment of the present application can be used to solve the problem of how to use a communication interface between two AMF entities to establish a PDU session between two networks.
- an embodiment of the present application provides another communication method.
- the second network is a private network
- the first AMF entity, the first UPF entity, and the first SMF entity in the second network are a visiting AMF (visit-AMF, V-AMF) entity and a visiting UPF (visit-UPF), respectively.
- the first network is the public network
- the second AMF entity, the second UPF entity, and the second SMF entity in the first network are the home AMF respectively (home-AMF, H-AMF) entity, home UPF (home-UPF, H-UPF) entity and home SMF (home-SMF, H-SMF) entity
- the terminal device is a UE as an example, as described below .
- S301 The UE sends a mobile management non-access stratum (MM NAS) message to the V-AMF entity.
- MM NAS mobile management non-access stratum
- the MM NAS message may be an example of the first message in FIG. 2 described above.
- the MM NAS message may include a PDU session establishment request (PDU session establishment request).
- the MM NAS message may include a session management (session management, SM) message, and the SM message may include a PDU session establishment request.
- SM session management
- the MM NAS message further includes at least one of S-NSSAI, a data network name DNN, a PDU session ID (PDU session ID), or a public network PDU session indication (public PDU session indication).
- the MM NAS message may be an uplink non-access stratum transmission (UL NAS NAS TRANSPORT) message.
- UL NAS NAS TRANSPORT uplink non-access stratum transmission
- the PDU session establishment request may carry a PDU type (PDU type), a service and a session continuity mode (SSC mode).
- PDU type may indicate that the PUD session is an IPV4 type or an IPV6 type.
- the service and session continuity mode may indicate the service and session continuity mode of the PDU session.
- the service and session continuity mode of the PDU session may be mode1, mode2, or mode3.
- mode1 means that the anchor point (UPF entity) of the IP address is unchanged, and it supports service continuity.
- mode2 means that the anchor point (UPF entity) of the IP address is variable, and in the process of establishing a new PDU session for the terminal device, the network first releases the old PDU session of the terminal device, and then notifies the terminal device to establish a new PDU session.
- mode3 means that the anchor point (UPF entity) of the IP address is variable, and in the process of establishing a new PDU session for the terminal device, the network first informs the terminal device to establish a new PDU session, and then releases the old PDU session of the terminal device.
- the V-AMF entity determines to establish a home routed PDU session for the UE.
- the V-AMF entity may determine to establish a home routed PDU session for the UE based on at least one of the S-NSSAI, the data network name DNN, or the public network PDU session indication in the MM NAS message, without establishing a local Network routed PDU session.
- the V-AMF entity may determine whether the PDU session requested by the UE allows local routing according to at least one of the S-NSSAI, the data network name DNN, or the public network PDU session indication. If the V-AMF entity determines that the PDU session requested by the UE does not If local routing is allowed, a home routed PDU session is established for the UE, otherwise a local routed PDU session is established for the UE.
- V-AMF entity selects a V-SMF entity.
- the V-AMF entity may select the auxiliary information and / or the data network name according to the network slice, and select the V-SMF entity.
- the above method further includes: the V-AMF entity selects the auxiliary information and / or the data network name according to the network slice, and selects the H-SMF entity.
- V-AMF entity sends a PDU session to the V-SMF entity to create a session management context request.
- the PDU session creation session management context request may create a session management context request (Nsmf_PDUSession_Create SMContext Request) for the PDU session of the network element SMF.
- the PDU session creation session management context request may be specifically an example of the second message in FIG. 2 described above.
- the PDU session creation session management context request carries a public network PDU session indication (public PDU session indication).
- V-SMF entity selects a V-UPF entity.
- the V-SMF entity creates a public network PDU session indication carried in the session management context request based on the PDU session.
- a UPF entity is selected from the private network's UPF entity resource pool, and the UPF entity can be used to communicate with the public network. Communication.
- V-SMF entity establishes an N4 session.
- the N4 session establishment process may include: the V-SMF entity sends a request message to the V-UPF entity, and the V-UPF entity sends a response message to the V-SMF entity.
- the access core network tunnel information (visit core network, V-CN, tunnel info) can be allocated by the V-SMF entity or the V-UPF entity.
- the access core network tunnel information can also be called private network core network tunnel information . If the access core network tunnel information is allocated by the V-SMF entity, the request message may carry the access core network tunnel information. If the access core network tunnel information is allocated by the V-UPF entity, the response message may carry the access core network tunnel information.
- V-SMF entity sends an N16 'message transmission request to the V-AMF entity.
- the N16 'message transmission request may specifically be an N16' message transmission request (Namf_communication_N16 'message transfer request) of the communication service of the network element AMF.
- the N16 'message transmission request may carry information about accessing the core network tunnel.
- the accessing core network tunnel information may be specifically an example of the first core network tunnel information shown in FIG. 2 described above.
- S307 may also be: the V-SMF entity sends a PDU session creation session management context response to the V-AMF entity, for example, the PDU session creation session management context response may specifically create a session management context response for the PDU session of the network element SMF (Nsmf_PDU session_CreateSMContext response).
- the PDU session creation session management context response carries access core network tunnel information.
- V-AMF entity sends an N14 'request message to the H-AMF entity.
- the N14 'request message may include at least one of network slice selection assistance information, a data network name, a PDU session establishment request, or access to core network tunnel information.
- the N14 'request message further includes identification information of the private network.
- the H-AMF entity sends a PDU session creation session management context request to the H-SMF entity.
- the PDU session creation session management context response may specifically be a PDU session creation session management context response of the network element SMF.
- the PDU session creation session management context request may include one or more of network slice selection assistance information, data network name, PDU session establishment request, or access to core network tunnel information.
- the PDU session creation session management context request also includes a VPLMN ID.
- the VPLMN ID can be used to indicate that the PDU session is a PDU session routed from the private network to the public network, or the VPLMN ID can be used to indicate that the type of the PDU session is a private network type. For example, certain bits in the VPLMN ID can be used to indicate that the VPLMN network is a private network.
- the V-AMF entity can identify the VPLMN ID of the network where the V-AMF entity that sent the N14' message is based on the configuration information, thereby determining the private network based on the VPLMN ID Identification information.
- the H-SMF entity registers the PDU session with the H-UDM entity, and obtains the session management subscription information of the UE from the H-UDM entity.
- the session management subscription information of the UE may include subscription information of a subscription permanent identifier (SUPI), NSSAI, or DNN.
- SUPI subscription permanent identifier
- NSSAI subscription permanent identifier
- DNN DNN
- S311 The H-SMF entity executes a PCF session management policy association establishment process (SM Policy, Establishment, Procedure).
- SM Policy Policy, Establishment, Procedure
- the H-SMF entity executes the PCF session management policy association establishment process, which may include: the H-SMF entity obtains the PCC rules of the PDU session from the PCF entity.
- steps S310 and S311 are optional steps.
- the H-SMF entity establishes an N4 session to the H-UPF entity for the PDU session.
- the N4 session establishment process may include: the H-SMF entity sends a request message to the H-UPF entity, and the H-UPF entity sends a response message to the request message to the H-SMF entity.
- the home core network tunnel information (home core network, H-CN, tunnel info) can be distributed by the H-SMF entity or the H-UPF entity.
- the home core network tunnel information can be the second in the process shown in FIG. 2 above. An example of core network tunnel information.
- the request message may carry the home core network tunnel information. If the home core network tunnel information is allocated by the H-UPF entity, the response message may carry the home core network tunnel information.
- the H-SMF entity sends an N16 'message transmission request to the H-AMF entity.
- the H-SMF entity may determine the current N9 tunnel (N9 tunnel) without establishing the N3 tunnel (N3 tunnel) according to the access core network tunnel information carried in the session management context request created by the PDU session in step S309. A N16 'message transmission request is returned to the H-AMF entity. Alternatively, the H-SMF entity may also determine the current N9 tunnel (N9 tunnel) without establishing the N3 tunnel (N3 tunnel) based on the VPLMN ID carried in the session management context request of the PDU session in step S309. -The AMF entity returns a N16 'message transmission request.
- the N16 'message transmission request may include one or more of the following information: QoS rules (QoS rules), protocol configuration options (PCO, PDU session selection type (PDU, Session type), SSC mode ( (SSC mode), home core network tunnel information (H-CN, Tunnel Info), QoS flow identifier (QFI), QoS profile (QoS profile), and aggregated maximum bitrate (Session-AMBR) .
- QoS rules QoS rules
- PCO protocol configuration options
- PDU PDU session selection type
- Session type Session type
- SSC mode SSC mode
- H-CN home core network tunnel information
- QFI QoS flow identifier
- QoS profile QoS profile
- Session-AMBR aggregated maximum bitrate
- S313 may also be: the H-SMF entity sends a PDU session to the H-AMF entity to create a session management context response.
- the PDU session creation session management context response may include one or more of the following information: QoS rules, PCO, PDU session selection type, SSC mode, home core network tunnel information, QFI (s), QoS configuration file, and Session -AMBR.
- S314 The H-AMF entity sends an N14 'message response (N14'message response) to the V-AMF entity.
- the N14 'message response may include one or more of QoS rules, PCO, PDU session selection type, SSC mode, home core network tunnel information, QFI (s), QoS configuration file, and Session-AMBR.
- the H-AMF entity can obtain the above QoS rules, PCO, PDU session selection type, SSC mode, and home core network tunnel information from the N16' message transmission request. , QFI (s), QoS configuration file, and Session-AMBR, and then the above parameters are carried in the N14 'message response, and the N14' message response is sent to the V-AMF entity in step S314.
- the above parameters are separately used as the cells in the N14 'message response.
- the H-AMF entity may directly carry the N16' message transmission request into the N14 'message response, and send the N14' message response to step S314. V-AMF entity.
- V-AMF entity sends a PDU session update session management context request to the V-SMF entity.
- the PDU session update session management context request may be a PDU session update session management context request (Nsmf_PDU Session_Update SMContext Request) of the network element SMF.
- Nsmf_PDU Session_Update SMContext Request PDU session update session management context request
- the PDU session update session management context request may include one or more of the above QoS rules, PCO, PDU session selection type, SSC mode, home core network tunnel information, QFI (s), QoS configuration file, and Session-AMBR. .
- the above parameters are also directly carried in the PDU session update session management context request, that is, the above parameters can be used alone as cells of the PDU session update session management context request.
- the above parameters are sent by the V-AMF entity to the V- SMF entity.
- the above parameters may be carried in a N16 'message transmission request, and the N16' message transmission request may be carried in a PDU session update session management context request.
- the above parameters are also sent by the V-AMF entity to the V-SMF entity through S315.
- the V-SMF entity sends a N1N2 message transmission request to the V-AMF entity.
- the N1N2 message transmission request may be a N1N2 message transmission request (Namf_communication_N1N2 message transfer request) for the transmission service of the network element AMF.
- the N1N2 message transmission request may include parameter information of the PDU session.
- the parameter information of the PDU session may include N1 SM information (N1 SM information) sent to the UE and first N2 SM information (N2 SM) sent to the RAN node. information).
- the N1SM information may include PDU Session Establishment Acceptance (PDU Session Establishment Acceptance).
- PDU Session Establishment Acceptance PDU Session Establishment Acceptance
- the establishment and acceptance of a PDU session may include an authorized QoS rule, an SSC mode, an S-NSSAI, an allocated IPv4 address, and a Session-AMBR.
- the first N2SM information may include a PDU session identifier, a QoS configuration file, core network tunnel information, S-NSSAI, and Session-AMBR.
- N2 PDU session request N2 PDU session request
- the N2 PDU session request may include N1 SM information and first N2 SM information.
- S318 The RAN node and the UE perform RRC message interaction.
- air interface resources can be established for the PDU session, and at the same time, N1 SM information can be sent to the UE.
- N2 PDU Session Response N2 PDU Session Response
- the N2 PDU session response may include PDU Session ID, Cause value, and second N2 SM information.
- the second N2 SM information may include PDU Session ID, RAN tunnel information (tunnel Info), and a list of accepted / rejected QoS profiles.
- the V-AMF entity sends a PDU session update session management context request to the V-SMF entity.
- the PDU session update session management context request may be an update session management context request of the PDU session of the network element SMF (Nsmf_PDU session_update SM context request).
- the PDU session update session management context request may carry second N2 SM information.
- the V-SMF entity sends an N4 session modification (N4 session modification) to the V-UPF entity.
- N4 session modification N4 session modification
- the N4 session modification may include RAN tunnel information.
- the V-SMF entity sends a PDU session update session management context response to the V-AMF entity.
- the PDU session update session management context response may be a PDU session update session management context response (Nsmf_PDU session_update SM context response) of the network element SMF.
- the UE may send a request to establish a PDU session from the private network home route to the public network to the private network AMF entity through the private network RAN node, and the private network AMF entity may send a request to the public network AMF entity, And the private network AMF allocates the core network tunnel information of the private network UPF side for the PDU session, and the public network AMF entity can allocate the public network UPF side core network tunnel information for the PDU session, thereby establishing a PDU session between the public and private network.
- an embodiment of the present application provides another communication method, which can be used to modify a PDU session between the first network and the second network.
- the first network may be a private network in the network architecture shown in FIG. 1B
- the second network may be a public network in the network architecture shown in FIG. 1B
- the first network may be a network architecture shown in FIG. 1A
- the second network may be a private network in the network architecture shown in FIG. 1A
- the terminal device may be a UE.
- S401 The UE generates a first message.
- the first message is used to request modification of a home route to a PDU session in the first network.
- the first message may be an existing message, for example, an uplink non-access stratum transmission message; it may also be a new message without limitation.
- S402 The UE sends a first message to the first AMF entity.
- the first message may include an N1SM message.
- the N1 SM message may include a PDU session modification request (PDU Session Modification Request).
- execution bodies of S401 and S402 can be replaced with RAN nodes.
- S403 The first AMF entity sends a second message to the second AMF entity.
- the first AMF entity may determine whether the PDU session is a PDU session that needs to be home-routed to the first network according to the stored information of the PDU session, and if so, send a second message to the second AMF entity.
- a second message is used to request modification of the PDU session, and the second message includes an N1SM message.
- the first AMF entity may mark the PDU session as a PDU session that needs to be home-routed to the first network.
- the second AMF entity sends a third message to the second SMF entity according to the second message.
- the third message includes the N1SM message, and the third message is used to request modification of the PDU session.
- the second AMF entity may mark the PDU session as a PDU session that needs to be home-routed to the first network.
- the third message may include second indication information, and the second indication information is used to indicate that the PDU session is a PDU session that is routed from the second network to the first network.
- S405a The second SMF entity sends the modified QoS parameter to the second AMF entity according to the third message.
- the modified QoS parameters are used to modify the corresponding QoS parameters of the PDU session on at least one of the first SMF entity, the first UPF entity, the RAN node, and the UE.
- the second SMF entity may mark the PDU session as a PDU session that needs to be home-routed to the first network.
- S405b If the second SMF entity determines that the parameters of the PDU session on the first UPF entity need to be modified according to the third message, initiate a N4 session modification process to the first UPF entity.
- the N4 session modification process is used to modify parameters of the PDU session on the first UPF entity.
- step S405b is an optional step.
- the second AMF entity sends the modified QoS parameter to the first AMF entity.
- the first AMF entity sends the modified QoS parameter to the first SMF entity.
- S408 If the first SMF entity determines that the parameters of the PDU session on the second UPF entity need to be modified according to the modified QoS parameters, initiate a N4 session modification process to the second UPF entity to modify the PDU session. Parameters on the second UPF entity.
- step S408 is an optional step.
- the first SMF entity may obtain the QoS configuration file and QoS rule of the modified PDU session according to the modified QoS parameter information, and the first SMF entity may send the QoS configuration file and For the QoS rule, the first AMF entity may send the modified QoS configuration file to the RAN node, and the first AMF entity may send the modified QoS rule to the UE.
- an embodiment of the present application provides another communication method.
- the communication method may modify a PDU session between a first network and a second network.
- the first network may be the network shown in FIG. 1B.
- the second network may be the public network in the network architecture shown in FIG. 1B, or the first network may be the public network in the network architecture shown in FIG. 1A, and the second network may be the network shown in FIG. 1A
- the terminal device may be a UE.
- the first network may further include a second UDM entity.
- the entire modification process may be triggered by the second UDM entity, or the entire modification process may be triggered by the second UPF entity, or the entire modification process may be triggered by the second SMF entity.
- the modification process triggered by the second SMF entity is taken as an example for description, and is not intended to limit the present application. This method is specifically described below.
- the second SMF entity generates modified QoS parameters, and the modified QoS parameters are used to modify corresponding QoS parameters of the PDU session on at least one of the first SMF entity, the first UPF entity, the RAN node, and the UE. .
- the second SMF entity sends the modified QoS parameter to the second AMF entity.
- S503 The second SMF entity initiates an N4 session modification process to the second UPF entity according to the modified Qos parameter to modify the parameters of the PDU session on the second UPF entity.
- the sequence of S502 and S503 is not limited.
- S504 The second AMF entity sends the modified QoS parameter to the first AMF entity.
- the first AMF entity sends the modified QoS parameter to the first SMF entity.
- the first SMF entity sends an N4 session modification process to the first UPF entity according to the modified QoS parameters to modify the parameters of the PDU session on the first UPF entity.
- the first SMF entity may send a QoS profile and / or a QoS rule obtained from the modified QoS parameters to the first AMF entity.
- the QoS profile may be carried in N2 SM information
- the QoS rule may be carried in N1 SM information
- the N1 SM info and / or N2 SM information may be carried in N1N2 message transmission and sent To the first AMF entity.
- the first AMF entity may send the QoS profile in the N1N2 message transmission to the RAN node, and / or send the QoS rule to the UE.
- the second SMF entity, the second UDM entity, or the second UPF entity can be triggered to modify the PDU session from the private network home route to the public network.
- an embodiment of the present application provides another communication method.
- the method uses a second network as a private network.
- the first AMF entity, the first UPF entity, and the first SMF entity in the second network are a V-AMF entity, a V-UPF entity, and a V-SMF entity, respectively.
- the first network is On the public network, the second AMF entity, the second UPF entity, and the second SMF entity in the first network are an H-AMF entity, an H-UPF entity, and an H-SMF entity, respectively.
- the UE is an example of a terminal device.
- the modification of the PDU session may be triggered by the UE, the modification of the PDU session may be triggered by the RAN node, and the modification of the PDU session may be triggered by the H-SMF entity.
- selection of A (Option A), selection of B (Option B), and selection of C (Option C) are taken as examples to describe the above three cases.
- option A may include S601a to S605a
- option B may include S601b to S604b
- option C may include S601c and S602c.
- Option A can be specifically:
- S601a The UE sends a PDU session modification request (PDU session modification request) to the V-AMF entity.
- the V-AMF entity determines that the PDU needs to be home-routed to the public network according to the stored PDU session information.
- the V-AMF entity may mark the PDU session as a PDU session that is routed from a private network home to a public network.
- S603a The V-AMF entity sends an N14 'request message (N14' message) to the H-AMF entity.
- the N14 'request message includes a PDU session modification request (PDU session modification request), and the PDU session modification request is used to modify QoS parameters of the PDU session.
- PDU session modification request PDU session modification request
- the H-AMF entity sends a PDU session update session management context request to the H-SMF entity.
- the PDU session update session management context request may be a PDU session update session management context request (Nsmf_PDU session_update SM context request) of the network element SMF, and the PDU session update session management context request may include a PDU session modification request (PDU session modification request).
- Nsmf_PDU session_update SM context request PDU session modification request
- the PDU session update session management context request may further include instruction information for instructing the PDU session to be routed from a private network home to a public network.
- the H-AMF entity may mark the PDU session as a PDU session that is routed from a private network home to a public network.
- the H-SMF entity sends a PDU session update session management context request response to the H-AMF entity.
- the PDU session update session management context request response may be a PDU session update session management context request response (Nsmf_PDU session_update SM context request response) of the network element SMF, and the PDU session update session management context request response may include a modified
- the modified QoS parameters are used to modify the corresponding QoS parameters of the PDU session on at least one of the V-SMF entity, the V-UPF entity, the RAN node, and the UE.
- the H-SMF entity may mark the PDU session as a PDU session that is routed from a private network home to a public network.
- step S605a the H-SMF entity sends an N16 'message transmission request to the H-AMF entity, and the N16' message transmission request carries the modified QoS parameter.
- the RAN node sends an N2 message (N2 message) to the V-AMF entity.
- the N2 message may include N2 SM information, a PDU session identifier, and the like.
- V-AMF entity sends an N14 'message to the H-AMF entity.
- the N14 'message is used to request modification of a PDU session.
- the N14 'message may include the N2 SM information, or the N2 SM information and a PDU session identifier.
- the V-AMF entity may mark the PDU session as a PDU session that is routed from a private network home to a public network.
- the H-AMF entity sends a PDU session update session management context request (PDU session update SM context request) to the H-SMF entity.
- PDU session update SM context request PDU session update SM context request
- the PDU session update SM context request includes the N2 SM information.
- the PDU session update session management context request may further include instruction information for indicating that the PDU session is routed from a private network home to a public network.
- the H-AMF entity may mark the PDU session as a PDU session that is routed from a private network home to a public network.
- the H-SMF entity sends a PDU session update session management context request response (PDU session update SM context request response) to the H-AMF entity.
- PDU session update SM context request response PDU session update SM context request response
- the PDU session update session management context request response may include a modified QoS parameter.
- the modified QoS parameters are used to modify corresponding QoS parameters of the PDU session on at least one entity of the first SMF entity, the first UPF entity, the RAN node, and the UE.
- the H-SMF entity may mark the PDU session as a PDU session that is routed from a private network home to a public network.
- step S604b is: the H-SMF entity sends an N16 'message transmission request to the H-AMF entity, and the N16' message transmission request carries the modified QoS parameter.
- the N16 'message may also be called an N16 message, and the N16 and N16' may correspond to the same interface, such as an interface between two SMF entities.
- the N14 'message may also be called an N14 message, and the N14 and N14' may correspond to the same interface, such as an interface between two AMF entities.
- S601c The H-SMF entity generates a modified QoS parameter.
- the entire modification process may be triggered by the H-PCF entity, or the entire modification process may be triggered by the H-UDM entity, or the entire modification process may be triggered by the H-SMF entity.
- the H-SMF entity sends a modified QoS parameter to the H-AMF entity, and the modified QoS parameter is used to modify the PDU session at least one entity of the first SMF entity, the first UPF entity, the RAN node, and the UE.
- the modified QoS parameter may be sent to the H-AMF entity through an N16 'message transmission request; or the modified QoS parameter may be sent to the H-AMF entity through a N1N2 message transmission request.
- the method may further include:
- S606 Perform N4 session modification (N4 session modification) between the H-SMF entity and the H-UPF entity.
- the N4 session modification is used to modify configuration parameters of the PDU session on the H-UPF entity.
- the H-AMF entity sends an N14 'message response (N14' message response) to the V-AMF entity.
- the N14 'message response may include a modified QoS parameter.
- the modified QoS parameter may be used as an information element of the N14 ′ message response, that is, the modified QoS parameter may be directly carried in the N14 ′ message response, and the modified QoS parameter may be H-
- the SMF entity sends it to the H-AMF entity through S605a or S604a or S602c; or, the modified QoS parameter can be carried in the N16 'message transmission request, and the N16' message can be carried in the N14 'message; or,
- the modified QoS parameters may be carried in a N1N2 message transmission request, and the N1N2 message transmission may be carried in a N14 'message.
- the V-AMF entity sends a PDU session update session management context request to the V-SMF entity, and the PDU session update session management context request may include a modified QoS parameter.
- the modified QoS parameter may be directly carried in a PDU session update session management context request, that is, the modified QoS parameter may be used alone as an information element of the SM context request for the PDU session update.
- the subsequent QoS parameters are sent by the H-AMF entity to the H-AMF entity through S607; or, the modified QoS parameters may be carried in a N16 'message transmission request, and the N16' message transmission request may be carried in a PDU session update.
- a session management context request; or, the modified QoS parameters may be carried in a N1N2 message transmission request, and the N1N2 message transmission request is carried in a PDU session update session management context request.
- the V-SMF entity sends an N1 / N2 message transmission (N1 / N2 message transfer) to the V-AMF entity.
- the V-SMF entity may obtain a QoS profile and / or a QoS rule from the modified QoS parameters.
- the QoS profile may be included in N2SM information
- the QoS rule may be included in N1SM information.
- the SMinfo and / or N2SMinfo may be included in the N1N2 message transmission and sent to the V-AMF entity.
- the V-AMF entity sends an N2 PDU session request to the RAN node.
- the N2 PDU session request may include N1 SM Info and / or N2 SM Info.
- S611 Perform RRC reconfiguration between the RAN node and the UE.
- the RAN node receives the N1 SM information in S6010, it sends it to the UE in the RRC reconfiguration procedure.
- N2 PDU session request response (N2 PDU session request request) to the V-AMF entity.
- V-AMF entity sends a PDU session update session management context request to the V-SMF entity.
- S614 Perform an N4 session modification between the V-SMF entity and the V-UPF entity to modify the configuration parameters on the V-UPF entity.
- the PDU session of the UE from the private network home route to the public network can be modified.
- this application provides a communication method that can release a PDU session between a first network and a second network.
- the first network may be as shown in FIG. 1B
- the private network in the network architecture the second network may be the public network in the network architecture shown in FIG. 1B, or the first network may be the public network in the network architecture shown in FIG. 1A, and the second network may be shown in FIG. 1A
- the terminal device may be a UE.
- the process is specifically:
- S701 The UE generates a first message, where the first message is used to request release of a PDU session with a home route to the first network.
- S702 The UE sends the first message to a first AMF entity.
- the first AMF entity sends a second message to the second AMF entity according to the first message, and the second message is used to request release of the PDU session.
- the first AMF entity may determine whether the PDU session is a PDU session that needs to be home-routed to the first network according to the stored information of the PDU session, and if it is, send the second AMF entity to the second AMF entity. A message, and the second message is used to request to release the PDU session.
- the V-AMF entity may mark the PDU session as a PDU session routed from a private network home route to a public network.
- S701 to S703 are: the first AMF entity sends a second message to the second AMF entity. That is, in the embodiment of the present application, the release of the PDU session of the home route may be triggered directly by the first AMF entity.
- the second AMF entity sends a third message to the second SMF entity according to the second message, and the third message is used to request release of the PDU session from the private network home route to the public network.
- the second AMF entity may mark the PDU session as a PDU session that is routed from a private network home to a public network.
- the second SMF entity sends a release parameter to the second AMF entity according to the third message, and the release parameter is used to release the PDU session from the private network home route to the public network.
- the second SMF entity may mark the PDU session as a PDU session routed from a private network home route to a public network.
- S705b The second SMF entity releases the configuration parameters of the PDU session configured on the second UPF entity according to the third message.
- the sequence of steps S705a and S705b is not limited.
- S706 The second AMF entity sends the release parameter to the first AMF entity.
- the first AMF entity sends the release parameter to the first SMF entity.
- the first SMF entity releases the configuration parameters of the PDU session configured on the first UPF entity according to the release parameter.
- the PDU session release parameter may include an N2 interface session management resource release request (N2, SM, Resource, Request) sent to the RAN node, and / or a PDU session release command (PDU Session, sent to the UE). Release Command).
- N2, SM, Resource, Request N2 interface session management resource release request
- PDU Session PDU Session
- the UE or the first AMF entity can trigger to release the UE's PDU session from the private network home route to the public network.
- this application provides a communication method, which can release a PDU session between a first network and a second network.
- the first network may be the network architecture shown in FIG. 1B
- the second network may be a public network in the network architecture shown in FIG. 1B, or the first network may be a public network in the network architecture shown in FIG. 1A, and the second network may be the network architecture shown in FIG. 1A.
- the terminal device may be a UE.
- the second SMF entity generates a release parameter, and the release parameter is used to release a UE's PDU session from a private network home route to a public network.
- the second SMF entity may mark the PDU session as a PDU session routed from a private network home route to a public network.
- the entire release process may be triggered by the second PCF entity, or the entire release process may be triggered by the second SMF entity.
- the second SMF entity is used to trigger the entire release process. It is not intended as a limitation on this application. If the entire release process is triggered by the second PCF entity, before step S801, the second PCF entity may further include sending a trigger command to the second SMF entity.
- S802a The second SMF entity sends the release parameter to the second AMF entity.
- S802b The second SMF entity releases the configuration parameters of the PDU session configured on the second UPF entity according to the release parameter.
- the sequence of S802a and S802b is not limited.
- the second AMF entity sends the release parameter to the first AMF entity.
- the second AMF entity may mark the PDU session as a PDU session that is routed from a private network home to a public network.
- the first AMF entity sends the release parameter to the first SMF entity.
- the first AMF entity may mark the PDU session as a PDU session that is routed from a private network home to a public network.
- the first SMF entity releases the configuration parameters of the PDU session configured on the first UPF entity according to the release parameter.
- the second SMF entity or the second UPF entity may be triggered to release the PDU session of the UE from the private network home route to the public network.
- the second network is a private network
- the first AMF entity, the first UPF entity, and the first SMF entity in the second network are a V-AMF entity, a V-UPF entity, and a V- An SMF entity
- the first network is a public network
- the second AMF entity, the second UPF entity, and the second SMF entity in the first network are an H-AMF entity, an H-UPF entity, and an H-SMF entity
- the terminal device is a UE as an example.
- this application provides a communication method. In the communication method shown in FIG.
- the release of the PDU session may be triggered by the UE, the release of the PDU session may be triggered by the RAN node, and the release of the PDU session may be triggered by the H-SMF entity.
- three cases of selecting A (Option A), selecting B (Option B), and selecting C (Option C) are used for description.
- option A may include S901a to S904a
- option B may include S901b to S904b
- option C may include S901c and S902c.
- Select A specifically: S901a: The UE sends an N1 mobility management message to the V-AMF entity.
- the N1 mobility management message may include a PDU session release request (PDU session release request).
- S902a The V-AMF entity sends an N14 'message to the H-AMF entity, where the N14' message is used to request the release of a PDU session.
- the N14 'message may include the PDU session release request.
- the V-AMF entity may mark the PDU session as a PDU session that is routed from a private network home to a public network.
- S903a The H-AMF entity sends a PDU session to the H-SMF entity to release a session management context request.
- the PDU session release session management context request may be a PDU session release session management context request (Nsmf_PDUsession_Release SM context request) of the network element SMF.
- the PDU session release session management context request may include a PDU session release request )Wait.
- the H-AMF entity may mark the PDU session as a PDU session that is routed from a private network home to a public network.
- the H-SMF entity sends a release parameter to the H-AMF entity to release the PDU.
- the release parameter may be included in a PDU session update session management context request response (PDU session update SM context request response); or, the release parameter may be included in a N16 'message transmission request.
- PDU session update SM context request response PDU session update SM context request response
- the H-SMF entity may mark the PDU session as a PDU session that is routed from a private network home to a public network.
- Option B may specifically be: S901b: the V-AMF entity triggers the release of a PDU session.
- S902b The V-AMF entity sends an N14 'message to the H-AMF entity, where the N14' message is used to request the release of a PDU session.
- the V-AMF entity may mark the PDU session as a PDU session that is routed from a private network home to a public network.
- S903b The H-AMF entity sends a PDU session to the H-SMF entity to release a session management context request.
- the PDU session release session management context request may be a PDU session release session management context request (Nsmf_PDUsession_Release SM context request) of the network element SMF, the PDU session release session management context request is used to release the UE from the private network home route A PDU session to the public network.
- Nsmf_PDUsession_Release SM context request a PDU session release session management context request of the network element SMF
- the H-AMF entity may mark the PDU session as a PDU session that is routed from a private network home to a public network.
- S904b The H-SMF entity sends a release parameter to the H-AMF entity to release the PDU.
- the release parameter may be used to release the UE's PDU session from a private network home route to a public network.
- the release parameter may be included in a PDU session release network element management context response, and the PDU session release network element management context response may be a network element SMF PDU session release network element management context response (Nsfm_PDUsession_ReleaseSM context context response). Or, the release parameter may be included in a N16 'message transmission request.
- the PDU session release network element management context response may be a network element SMF PDU session release network element management context response (Nsfm_PDUsession_ReleaseSM context response).
- the release parameter may be included in a N16 'message transmission request.
- the H-SMF entity may mark the PDU session as a PDU session that is routed from a private network home to a public network.
- Option C may be specifically: S901c:
- the H-SMF entity generates a release parameter, and the release parameter may be used to release the UE's PDU session from the private network home route to the public network.
- the entire release process may be triggered by the H-PCF, or the entire release process may be triggered by the H-SMF entity.
- S902c The H-SMF entity sends the release parameter to the H-AMF entity.
- the release parameter may be included in a N16 'message transmission request; or the release parameter may be included in a N1N2 message transmission request.
- the H-SMF entity may mark the PDU session as a PDU session that is routed from a private network home to a public network.
- the method may further include:
- N4 session release (N4 session release) is performed between the H-SMF entity and the H-UPF entity.
- the N4 session release is used to release the configuration parameters of the PDU session configured on the H-UPF entity.
- the H-AMF entity sends an N14 'message response (N14' message response) to the V-AMF entity.
- the N14 'message response may include the release parameter.
- the release parameter may be used alone as an N14 'message response cell, that is, the release parameter may be directly carried in the N14' message response, and the release parameter is sent by the H-AMF entity to the V-AMF through S907. Entity; or the release parameter may be carried in a N16 'message transmission request, the N16' message transmission request may be carried in a N14 'message response; or the release parameter may be carried in a N1N2 message transmission request, the The N1N2 message transmission request is carried in the N14 'message response.
- V-AMF entity sends a PDU session update session management context request to the V-SMF entity.
- the PDU session update session management context request may include the release parameter.
- the release parameter may be used alone as an information element of a PDU session update session management context request, that is, the release parameter may be directly carried in the PDU session update session management context request; or the release parameter may be carried in N16 'In a message transmission request, the N16' message transmission request is carried in a PDU session update session management context request; or, the release parameter may be carried in a N1N2 message transmission request, and the N1N2 message transmission request may be carried in a PDU session Update in session management context request.
- S908 is: the V-AMF entity sends a PDU session to the V-SMF entity to release the session management context request.
- the PDU session release session management context request may include the release parameter.
- the release parameter may be used alone as a cell for a PDU session release session management context request, and the release parameter may be directly carried in the PDU session release session management context request; or the release parameter may be carried in N16 ' In the message transmission request, the N16 'message transmission request is carried in a PDU session release session management context request; or, the release parameter may be carried in a N1N2 message transmission request, and the N1N2 message transmission request is carried in a PDU session release session Management context request.
- the V-SMF entity sends a release parameter to the V-AMF entity for releasing the PDU session
- the release parameter of the PDU session may include an N2 interface session management resource release request (N2SMResourceRelease) sent to the RAN node. request) and / or a PDU session release command (PDU Session Release Command) sent to the UE.
- N2SMResourceRelease N2 interface session management resource release request
- PDU Session Release Command PDU Session Release Command
- the release parameter may be carried in an update session management context response of the PDU session; or the release parameter may be carried in a N1 / N2 message transfer (N1 / N2 message transfer); or The release parameter may be carried in a PDU session release session management context response.
- N-session release is performed between the V-SMF entity and the V-UPF entity, and the N4 session release is used to release the configuration parameters of the PDU session configured on the V-UPF entity.
- the sequence of steps S909 and S9010 is not limited.
- the V-AMF entity sends an N2 PDU session request to the RAN node.
- the N2 PDU session request may include an N2 interface session management resource release request (N2, SM, Resource, Request) and a PDU session release command (PDU, Session, Release Command).
- S9012 Perform RRC reconfiguration between the RAN node and the UE.
- the RAN node may send the PDU Session Release Command to the UE in an RRC reconfiguration process.
- N2 PDU session request response (N2 PDU session request request) to the V-AMF entity.
- V-AMF entity sends a PDU session update session management context request to the V-SMF entity.
- the release of the PDU session may be triggered by the UE, the release of the PDU session may be triggered by the RAN node, and the release of the PDU session may be triggered by the H-SMF entity.
- the present application provides a communication device 1000.
- the communication device 1000 may include a processing unit 1001 and a transceiving unit 1002.
- the communication device 1000 may be applied to a terminal device or a chip in a terminal device, and is configured to execute FIG. 2, FIG. 3, FIG. 4, FIG. 5, FIG. 6, FIG. 7, FIG. 8, or FIG.
- the terminal device is the main execution step.
- the processing unit 1001 may be configured to generate a first message
- the transceiver unit 1002 may be configured to send the first message to a first AMF entity.
- the communication device 1000 may be applied to a first AMF entity or a chip in the first AMF entity, and is configured to execute FIG. 2, FIG. 3, FIG. 4, FIG. 5, FIG. 6, FIG. 7, In the process shown in FIG. 8 or FIG. 9, steps using the first AMF entity as an execution subject.
- the transceiver unit 1002 may be configured to receive a first message from the terminal device, and the processing unit 1001 may be configured to control the transceiver unit 1002 to send a second message to the first SMF entity according to the first message, and the second message is used to request
- the core network tunnel information of the PDU session may be configured to receive the first core network tunnel information from the first SMF entity, and send the first core network tunnel information to a second AMF entity;
- the first core network tunnel information is used to establish a data channel of the PDU session between a first user plane function UPF entity and the UPF entity in the first network;
- the communication device 1000 may be applied to a first SMF entity or a chip in the first SMF entity, and is configured to execute FIG. 2, FIG. 3, FIG. 4, FIG. 5, FIG. 6, FIG. 7, In the process shown in FIG. 8 or FIG. 9, the first SMF entity is used as the execution subject.
- the transceiver unit 1002 may be configured to receive a second message from the first access and mobility management function AMF entity, the second message is used to request core network tunnel information of the PDU session; the transceiver unit 1002 may be configured to send The first AMF entity sends a first core network tunnel message, and the first core network tunnel information is used to establish a data channel for the PDU session between a first user plane function UPF entity and a UPF entity in the first network.
- the communication device 1000 may be applied to a second AMF entity or a chip in a second AMF entity, and is configured to execute FIG. 2, FIG. 3, FIG. 4, FIG. 5, FIG. 6, FIG. 7, In the process shown in FIG. 8 or FIG. 9, the steps using the second AMF entity as an execution subject.
- the transceiver unit 1002 may be configured to receive first core network tunnel information from the first AMF entity, where the first core network tunnel information is used to establish a PDU session between the first user plane function UPF entity and the UPF entity in the first network. Data channel; the transceiver unit 1002 is further configured to send the first core network tunnel information to a second SMF entity.
- the communication device 1000 may be applied to a second SMF entity or a chip in a second SMF entity, and is configured to execute FIG. 2, FIG. 3, FIG. 4, FIG. 5, FIG. 6, FIG. 7, In the process shown in FIG. 8 or FIG. 9, the steps are performed by using the second SMF entity as an execution subject.
- the transceiver unit 1002 may be configured to receive first core network tunnel information from the second AMF entity, where the first core network tunnel information is used to establish a PDU session between the first user plane function UPF entity and the UPF entity in the first network. Data channel; the transceiver unit 1002 may be configured to send second core network tunnel information to the second AMF entity, and the second core network tunnel information is used to establish the PDU session between the first UPF entity and the second Data channel between UPF entities.
- processing unit 1001 and the transceiver unit 1002 For specific functions of the processing unit 1001 and the transceiver unit 1002, refer to the description of the processes shown in FIG. 2, FIG. 3, FIG. 4, FIG. 5, FIG. 6, FIG. 7, FIG. 8 or FIG.
- the present application further provides a communication device 1100.
- the communication device 1100 can be applied to the terminal device or a chip in the terminal device in the processes shown in FIG. 2 to FIG. 9, and can also be applied.
- the first AMF entity or the chip in the first AMF entity in the processes shown in FIG. 2 to FIG. 9 may also be applied to the first SMF entity or the first SMF entity in the processes shown in FIG. 2 to FIG. 9.
- the chip can also be applied to the second AMF entity or the chip in the second AMF entity in the processes shown in FIG. 2 to FIG. 9 above, and it can also be applied to the second SMF entity in the processes shown in FIG. 2 to FIG. 9 above.
- the chip in the second SMF entity is not limited herein.
- the communication device 1100 may include a processor 1101 and a memory 1102. Further, the device may further include a receiver 1104 and a transmitter 1105. Further, the device may further include a bus system 1103.
- the processor 1101, the memory 1102, the receiver 1104, and the transmitter 1105 may be connected through a bus system 1103.
- the memory 1102 may store instructions, and the processor 1101 may execute instructions stored in the memory 1102 to control the receiver 1104 to receive. Signals, and control the transmitter 1105 to send signals to complete the steps in the methods shown in FIG. 2 to FIG. 9 that mainly take the terminal device, the first SMF entity, the first AMF entity, the second SMF entity, or the second AMF entity as the main body.
- the receiver 1104 and the transmitter 1105 may be different physical entities or the same physical entity, and may be collectively referred to as a transceiver.
- the memory 1102 may be integrated in the processor 1101, or may be a physical entity different from the processor 1101.
- the functions of the receiver 1104 and the transmitter 1105 may be considered to be implemented through a transceiver circuit or a dedicated chip for transceiver.
- the processor 1101 may be considered to be implemented by a dedicated processing chip, a processing circuit, a processor, or a general-purpose chip.
- a computer manner may be considered to implement the functions of the network device or the terminal device provided in the embodiments of the present application.
- Program code that is about to implement the functions of the processor 1101, the receiver 1104, and the transmitter 1105 is stored in the memory 1102.
- the general-purpose processor can implement the functions of the processor 1101, the receiver 1104, and the transmitter 1105 by executing the code in the memory.
- the communication device 1100 may be applied to a terminal device or a chip in a terminal device.
- the communication device 1100 may be used to execute the processes shown in FIG. 2 to FIG. step.
- the processor 1101 may be configured to generate a first message
- the sender 1105 may be configured to send a first message to a first AMF entity.
- the communication device 1100 may be applied to a first AMF entity or a chip in the first AMF entity.
- the communication device 1100 may be used to execute the processes shown in FIG. 2 to FIG.
- the AMF entity is the step of the execution subject.
- the receiver 1104 may be used to receive a first message from a terminal device
- the processor 1101 may be used to control the sender 1105 to send a second message according to the first message
- the receiver 1104 may be used to receive a first message from the first SMF entity. Tunnel information of the first core network.
- the communication device 1100 may be used for a first SMF entity or a chip in the first SMF entity.
- the communication device 1100 may be used for executing the processes shown in FIG. 2 to FIG.
- An entity is a step that executes the subject.
- the receiver 1104 may be configured to receive a second message from the first AMF entity
- the transmitter 1105 may be configured to send a first core network tunnel message to the first AMF entity.
- the communication device 1100 may be applied to a second AMF entity or a chip in a second AMF entity.
- the communication device 1100 may be used to execute the processes shown in FIG. 2 to FIG.
- the AMF entity is the step of the execution subject.
- the receiver 1104 may be used to receive the first core network tunnel information from the first AMF entity
- the sender 1105 may be used to send the first core network tunnel information to the second SMF entity.
- the communication device 1100 may be applied to a second SMF entity or a chip in the second SMF entity.
- the communication device 1100 may be used to execute the processes shown in FIG. 2 to FIG.
- the SMF entity is the step of the execution subject.
- the receiver 1104 may be used to receive the first core network tunnel information from the second AMF entity
- the sender 1105 may be used to send the second core network tunnel information to the second AMF entity.
- the processor 1101, the receiver 1104, and the transmitter 1105 refer to the description of the processes shown in FIG. 2 to FIG. 9 above, and details are not described herein again.
- FIG. 12 provides a schematic structural diagram of a terminal device.
- the terminal device can be applied to the processes shown in FIG. 2 to FIG. 9.
- the terminal device is the main execution step.
- FIG. 12 only The main components of the terminal device are shown.
- the terminal device 1200 may include a processor, a processor, a memory, and a control circuit.
- the terminal device 1200 may further include an antenna and / or an input / output device.
- the processor may be used for processing communication protocols and communication data, and controlling user equipment, executing software programs, and processing data of the software programs.
- the memory may store software programs and / or data.
- the control circuit can be used for converting baseband signals to radio frequency signals and processing radio frequency signals.
- the control circuit and the antenna can also be called a transceiver, which can be used to send and receive radio frequency signals in the form of electromagnetic waves.
- Input-output devices such as touch screens, display screens, keyboards, etc., can be used to receive data input by the user and output data to the user.
- the processor may read the software program in the storage unit, interpret and execute the instructions of the software program, and process the data of the software program.
- the processor performs baseband processing on the data to be sent, and then outputs the baseband signal to the radio frequency circuit.
- the radio frequency circuit processes the baseband signal, the radio frequency signal is sent out in the form of electromagnetic waves through the antenna.
- the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor.
- the processor converts the baseband signal into data and processes the data.
- FIG. 12 shows only one memory and a processor. In an actual user equipment, there may be multiple processors and memories.
- the memory may also be referred to as a storage medium or a storage device, which is not limited in the embodiment of the present application.
- the processor may include a baseband processor and a central processor.
- the baseband processor may be used to process communication protocols and communication data
- the central processor may be used to control the entire user equipment and execute software programs. Processing data from software programs.
- the processor in FIG. 12 integrates the functions of the baseband processor and the central processing unit.
- the baseband processor and the central processing unit may also be independent processors, which are interconnected through technologies such as a bus.
- the terminal device may include multiple baseband processors to adapt to different network standards, the terminal device may include multiple central processors to enhance its processing capabilities, and various components of the terminal device may be connected through various buses.
- the baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip.
- the central processing unit can also be expressed as a central processing circuit or a central processing chip.
- the function of processing communication protocols and communication data may be built in the processor or stored in the storage unit in the form of a software program, and the processor executes the software program to implement the baseband processing function.
- an antenna and a control circuit having a transmitting and receiving function may be used as the transmitting and receiving unit 1201 of the terminal device 1200, and a processor having a processing function may be regarded as the processing unit 1202 of the terminal device 1200.
- the terminal device 1200 may include a transceiver unit 1201 and a processing unit 1202.
- the transceiver unit may also be referred to as a transceiver, a transceiver, a transceiver device, and the like.
- the device for implementing the receiving function in the transceiver unit 1201 may be regarded as a receiving unit, and the device for implementing the transmitting function in the transceiver unit 1201 may be regarded as a transmitting unit, that is, the transceiver unit 1201 includes a receiving unit and a transmitting unit.
- the receiving unit may also be called a receiver, a receiver, a receiving circuit, and the like
- the sending unit may also be called a transmitter, a transmitter, or a transmitting circuit.
- the network device in each of the foregoing device embodiments corresponds exactly to the network device or terminal device in the terminal device and method embodiments, and the corresponding module or unit performs the corresponding steps, such as the sending module (transmitter) method execution method implementation
- the receiving module executes the steps received in the method embodiment.
- Other steps than sending and receiving can be performed by the processing module (processor).
- the sending module and the receiving module can form a transceiver module, and the transmitter and the receiver can form a transceiver to realize the transmitting and receiving function together; the processor can be one or more.
- the embodiment of the present application further provides a communication system including the foregoing terminal device, a first AMF entity, a first SMF entity, a second AMF entity, a second SMF entity, and the like.
- an embodiment of the present application further provides a computer storage medium.
- a software program is stored in the storage medium, and the software program can implement any one or more of the foregoing when read and executed by one or more processors.
- the computer storage medium may include various media that can store program codes, such as a U disk, a mobile hard disk, a read-only memory, a random access memory, a magnetic disk, or an optical disk.
- an embodiment of the present application further provides a chip that includes a processor, and is configured to implement a function involved in any one or more of the foregoing embodiments, such as obtaining or processing information involved in the foregoing method, or Message.
- the chip further includes a memory, which is configured to store program instructions and data executed by the processor.
- the chip can also include chips and other discrete devices.
- the processor may be a central processing unit (CPU), and the processor may also be another general-purpose processor, a digital signal processor (DSP), or a special-purpose integration.
- Circuit application-specific integrated circuit, ASIC
- ready-made programmable gate array field programmable gate array, FPGA
- a general-purpose processor may be a microprocessor, or any conventional processor or the like.
- the memory may include read-only memory and random access memory, and provide instructions and data to the processor.
- a portion of the memory may also include non-volatile random access memory.
- the bus system may also include a power bus, a control bus, and a status signal bus.
- various buses are marked as a bus system in the figure.
- each step of the above method may be completed by an integrated logic circuit of hardware in a processor or an instruction in a form of software.
- the steps of the method disclosed in combination with the embodiments of the present application may be directly implemented by a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
- the software module may be located in a mature storage medium such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, and the like.
- the storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the foregoing method in combination with its hardware. To avoid repetition, it will not be described in detail here.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
一种通信方法及装置,该方法为:终端设备向第一AMF实体请求建立归属路由到第一网络的PDU会话,第一AMF实体根据该请求向第一SMF实体请求PDU会话的第一核心网隧道信息,并向第二AMF实体发送该第一核心网隧道信息,第二AMF实体将该第一核心网隧道信息通过第二SMF实体发送给第二UPF实体,并从第二UPF实体获取到该PDU会话的第二核心网隧道信息,将该第二核心网隧道信息通过第一AMF实体和第一SMF实体发送给第一UPF实体,在第一UPF实体以及第二UPF实体之间建立PDU会话。
Description
相关申请的交叉引用
本申请要求在2018年09月30日提交中国专利局、申请号为201811161320.X、申请名称为“一种通信方法及装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
本申请涉及通信技术领域,尤其涉及一种通信方法及装置。
在未来的第五代(5th-generation,5G)移动通信***中,垂直行业是一个十分重要的领域,例如,物联网(internet of things,IoT)、机器与机器对话(machine to machine,M2M)以及工业4.0等。由于在垂直行业中存在大量的私有企业,且这些私有企业不但期望采用快速、可靠的第三代合作伙伴计划(3rd generation partnership project,3GPP)技术实现企业园区的覆盖,还期望对企业园区内的移动设备进行管理和控制,例如,用户签约、保护用户隐私以及保护私网业务数据安全等,而不依赖于运营商网络。一种可能的解决方式是:私有企业自己布署企业私网,实现企业园区的网络覆盖。
但是,为了企业私网和运营商公网的互联互通,公网运营商强烈要求私网用户在公网开户,即由公网的统一数据管理功能(unified data management,UDM)实体对私网用户进行签约管控。公网运营商的要求明显违背了私有企业对企业私网的期望。
针对上述问题,现有技术中定义了一种公网与私网互通的架构:企业私网与运营商公网在核心网进行互通对接;同时,为了保护双方的安全,双方可由统一的代理(proxy)服务器作为路由节点。但基于上述公网与私网互通的架构,企业私网与运营商公网之间如何进行通信需要进一步探讨。
发明内容
第一方面,提供一种通信方法及装置,该方法可应用于终端设备,包括:终端设备生成第一消息,所述第一消息用于请求建立归属路由到第一网络中的协议数据单元PDU会话;所述终端设备向第一接入和移动性管理功能AMF实体发送所述第一消息,所述第一AMF实体为第二网络中的网元。
通过上述方案,当终端设备位于第二网络的服务范围时,第二网络可通过第二网络的RAN节点发送请求建立归属路由到第一网络的PDU会话,利用该PDU会话,终端设备可实现应用第一网络所提供的数据业务。比如,第二网络可为私网,第一网络可为公网,或者,第二网络为公网,第一网络为私网。
在一种可能的实现中,所述第一消息中包括第一指示信息,所述第一指示信息用于指示所述PDU会话为归属路由到所述第一网络中的PDU会话。
在一种可能的实现中,所述第一指示信息包括数据网络名、切片选择信息、网络类型 指示信息或所述第一网络的标识信息中的至少一个。利用数据网络名、切片选择信息、网络类型指示信息或第一网络的标识信息,第一AMF实体可确定终端设备请求建立的PDU会话为本地路由或归属路由,所述归属路由又可称为不允许本地路由。
在一种可能的实现中,所述第一消息包括数据网络名或切片选择信息中的至少一个。针对上述可能实现,一种应用场景中,第一消息中不包括第一指示信息,仅包括数据网络名或切片选择信息,利用该数据网络名或切片选择信息,第一AMF实体可确定终端设备请求建立的PDU会话为本地路由或归属路由,相对于在第一消息中添加第一指示信息的方案,可节省信令开销。
第二方面,提供一种通信方法,该方法可应用于第一AMF实体,包括:第一接入和移动性管理功能AMF实体接收来自终端设备的第一消息,所述第一消息用于请求建立归属路由到第一网络的协议数据单元PDU会话;所述第一AMF实体根据所述第一消息,向第一会话管理功能SMF实体发送第二消息,所述第二消息用于请求所述PDU会话的核心网隧道信息;所述第一AMF实体接收来自所述第一SMF实体的第一核心网隧道信息,并向第二AMF实体发送所述第一核心网隧道信息,所述第一核心网隧道信息用于建立所述PDU会话在第一用户面功能UPF实体与所述第一网络中UPF实体之间的数据通道;其中,所述第一AMF实体、所述第一SMF实体和第一用户面功能UPF实体为第二网络中的网元,所述第二AMF实体为所述第一网络中的网元。
通过上述方案,终端设备向第二网络中的AMF实体请求建立路由到第一网络的PDU会话,第二网络中的AMF实体根据该请求向第二网络中的SMF实体请求PDU会话的第一核心网隧道信息,并向第一网络中的AMF实体发送该第一核心网隧道信息,第一网络中的AMF实体将该第一核心网隧道信息通过第一网络中的SMF实体发送给第一网络中的UPF实体,并从第一网络中的UPF实体获取到该PDU会话的第二核心网隧道信息,进一步将该第二核心网隧道信息通过第二网络中的AMF实体和SMF实体发送给第二网络中的UPF实体,实现了在第一网络中的UPF实体以及第二网络中的UPF实体之间成功建立了PDU会话,即通过两个网络中AMF实体之间的通信接口成功地建立两个网络中UPF实体之间PDU会话,进而解决了公网和私网之间通信问题。
在一种可现的实现中,所述第一消息包括第一指示信息,所述第一指示信息用于指示所述PDU会话为归属路由到所述第一网络中的PDU会话。
在一种可现的实现中,所述第一指示信息包括数据网络名、切片选择信息、网络类型指示信息或所述第一网络的标识信息中的至少一个。
在一种可现的实现中,所述第二消息包括所述第一指示信息。
在一种可现的实现中,所述第一消息中包括数据网络名和/或切片选择信息,所述方法还包括:所述第一AMF实体根据数据网络名和/或切片选择信息与指示信息的对应关系,确定与所述第一消息中的数据网络名和/或切片选择信息所对应的指示信息;当所述第一消息中的数据网络名和/或切片选择信息所对应的指示信息用于指示所述PDU会话不允许本地路由时,所述第一AMF实体根据所述终端设备的标识,确定所述PDU会话的归属网络为所述第一网络,或者,所述第一AMF实体根据所述终端设备的签约信息中包括的数据网络名和/或切片选择信息与归属路由网络标识的对应关系,确定所述PDU会话的归属网络为所述第一网络。
通过上述方法,第一AMF实体可具体确定PDU会话需要归属路由的网络。
在一种可现的实现中,所述第二消息中包括第二指示信息;其中,当所述第一网络为私网且所述第二网络为公网时,所述第二指示信息用于指示所述请求建立的PDU会话的类型为私网类型;或者,当所述第一网络为公网且所述第二网络为私网时,所述第二指示信息用于指示所述请求建立的PDU会话的类型为公网类型。
在一种可现的实现中,所述方法还包括:所述第一AMF实体选择第二SMF实体,所述第二SMF实***于所述第一网络。
在一种可现的实现中,所述第二消息中包括所述第二SMF实体的标识;其中,当所述第一网络为私网时,所述第二SMF实体的标识用于指示所述第二SMF实体为私网中的SMF实体;或者,当所述第一网络为公网时,所述第二SMF实体的标识用于指示所述第二SMF实体为公网中的SMF实体。
在一种可现的实现中,所述方法还包括:所述第一AMF实体向所述第二AMF实体发送切片选择信息、数据网络名、PDU会话建立请求或所述第二网络的标识信息中的至少一个。
在一种可现的实现中,所述方法还包括:所述第一AMF实体接收来自所述第二AMF实体的第二核心网隧道信息,所述第二核心网隧道信息用于建立所述PDU会话在所述第一UPF实体与所述第一网络中第二UPF实体之间的数据通道;所述第一AMF实体向所述第一SMF实体发送所述第二核心网隧道信息。
在一种可现的实现中,所述方法还包括:所述第一AMF实体接收来自所述第二AMF实体的所述PDU会话的服务质量QoS参数信息;所述第一AMF实体向所述第一SMF实体发送所述PDU会话的QoS参数信息;所述第一AMF实体接收来自所述第一SMF实体的QoS配置文件和QoS规则;所述第一AMF实体向无线接入网设备发送所述QoS配置文件;所述第一AMF实体向终端设备发送所述QoS规则。
在一种可能的实现中,所述第二消息为创建PDU会话的上下文请求;所述第一核心网隧道信息携带在所述创建PDU会话的上下文响应中,或者,所述第一核心网隧道信息携带在N16’消息传输请求中。
第三方面,提供一种通信方法,该通信方法应用于第一SMF实体,可包括:第一会话管理功能SMF实体接收来自第一接入和移动性管理功能AMF实体的第二消息,所述第二消息用于请求协议数据单元PDU会话的核心网隧道信息;所述第一SMF实体根据所述第二消息,向所述第一AMF实体发送第一核心网隧道消息,所述第一核心网隧道信息用于建立所述PDU会话在第一用户面功能UPF实体与第一网络中UPF实体之间的数据通道;其中,所述第一AMF实体、所述第一SMF实体和所述第一UPF实体为第二网络中的网元。
在一种可现的实现中,所述第二消息中包括第一指示信息;其中,当所述第一网络为私网时,所述第二指示信息用于指示所述请求建立的PDU会话的类型为私网类型;或者,当所述第一网络为公网时,所述第二指示信息用于指示所述请求建立的PDU会话的类型为公网类型。
在一种可现的实现中,所述第二消息中包括所述第二指示信息,所述第二指示信息用于指示所述PDU会话的类型为私网类型或公网类型。
在一种可现的实现中,所述第二消息中包括所述第二SMF实体的标识;其中,当所述第一网络为私网时,所述第二SMF实体的标识用于指示所述第二SMF实体为私网中的 SMF实体;当所述第一网络为公网时,所述第二SMF实体的标识用于指示所述第二SMF实体为公网中的SMF实体。
在一种可现的实现中,所述方法还包括:所述第一SMF实体根据所述第一指示信息或所述第二指示信息,确定所述第一UPF实体;所述第一SMF实体为所述第一UPF实体分配所述第一核心网隧道信息;所述第一SMF实体向所述第一UPF实体发送所述第一核心网隧道信息。
在一种可现的实现中,所述方法还包括:所述第一SMF实体接收来自所述第一AMF实体的第二核心网隧道信息,所述第二核心网隧道信息用于建立所述PDU会话在所述第一UPF实体与所述第一网络中第二UPF实体之间的数据通道;所述第一SMF实体向所述第一UPF实体发送所述第二核心网隧道信息。
在一种可现的实现中,所述方法还包括:所述第一SMF实体接收来自所述第一AMF实体的QoS参数信息;所述第一SMF实体根据所述QoS参数信息,获取所述PDU会话的QoS配置文件和QoS规则;所述第一SMF实体向所述第一AMF实体发送所述QoS配置文件和所述QoS规则。
在一种可能的实现中,所述第二消息为创建PDU会话的上下文请求;所述第一核心网隧道消息携带在所述创建PDU会话的上下文响应中,或者,所述第一核心网隧道信息携带在N16’消息传输请求中。
第四方面,提供一种通信方法,该通信方法可应用于第二AMF实体,包括:第二接入和移动性管理功能AMF实体接收来自第一AMF实体的第一核心网隧道信息,所述第一核心网隧道信息用于建立协议数据单元PDU会话在第一用户面功能UPF实体与第一网络中UPF实体间的数据通道;所述第二AMF实体向第二会话管理功能SMF实体发送所述第一核心网隧道信息;其中,所述第二AMF实体和所述第二SMF实体为所述第一网络中的网元,所述第一AMF实体和所述第一UPF实体为第二网络中的网元。
在一种可现的实现中,所述方法还包括:所述第二AMF实体向所述第二SMF实体发送第三指示信息,所述第三指示信息用于指示所述PDU会话为从所述第二网络归属路由到所述第一网络的PDU会话。
在一种可现的实现中,所述第三指示信息中包括所述第二网络的标识信息。
在一种可现的实现中,所述方法还包括:所述第二AMF实体接收来自所述第二SMF实体的第二核心网隧道信息,所述第二核心网隧道信息用于建立所述PDU会话在所述第一UPF实体和所述第一网络中第二UPF实体间的数据通道;所述第二AMF实体向所述第一AMF实体发送所述第二核心网隧道信息。
在一种可现的实现中,所述方法还包括:所述第二AMF实体接收来自所述第二SMF实体的所述PDU会话的QoS参数信息;所述第二AMF实体向所述第一AMF实体发送所述PDU会话的QoS参数信息。
在一种可能的实现中,所述第二消息为创建PDU会话的上下文请求;所述第一核心网隧道信息携带在所述创建PDU会话的上下文响应中,或者,所述第一核心网隧道信息携带在N16’消息传输请求中。
在一种可能的实现中,所述第一核心网隧道信息携带在创建PDU会话的上下文请求中;
所述第二核心网隧道信息携带在创建PDU会话的上下文响应中,或者,所述第二核 心网隧道信息携带在N16’消息传输请求中。
第五方面,提供一种通信方法,该通信方法可应用于第二SMF实体,包括:第二会话管理功能SMF实体接收来自第二接入和移动性管理功能AMF实体的第一核心网隧道信息,所述第一核心网隧道信息用于建立协议数据单元PDU会话在第一用户面功能UPF实体与第一网络中UPF实体之间的数据通道;所述第二SMF实体向所述第二AMF实体发送第二核心网隧道信息,所述第二核心网隧道信息用于建立所述PDU会话在所述第一UPF实体与第二UPF实体之间的数据通道;其中,所述第一UPF实体为第二网络中的网元,所述第二AMF实体、所述第二SMF实体和所述第二UPF实体为所述第一网络中的网元。
在一种可现的实现中,所述方法还包括:所述第二SMF实体接收来自所述第二AMF实体的第三指示信息;其中,所述第三指示信息用于指示所述PDU会话为从所述第二网络归属路由到所述第一网络的PDU会话。
在一种可现的实现中,所述第三指示信息中包括所述第二网络的标识信息。
在一种可现的实现中,所述方法还包括:所述第二SMF实体根据所述第三指示信息,确定所述第二UPF实体;所述第二SMF实体为所述第二UPF实体分配所述第二核心网隧道信息;所述第二SMF实体向所述第二UPF实体发送所述第二核心网隧道信息。
在一种可现的实现中,所述方法还包括:所述第二SMF实体向所述第二AMF实体发送QoS参数信息。
在一种可能的实现中,所述第一核心网隧道信息携带在创建PDU会话的上下文请求中;
所述第二核心网隧道信息携带在创建PDU会话的上下文响应中,或者,所述第二核心网隧道信息携带在N16’消息传输请求中。
第六方面,提供一种通信装置,该装置具有实现上述第一方面和第一方面的任一种可能的设计中终端设备行为的功能。所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中,该装置可以是芯片或者集成电路。
在一个可能的设计中,该装置包括存储器和处理器,存储器存储有一组程序,处理器用于执行存储器存储的程序,当程序被执行时,所述装置可以执行上述第一方面和第一方面的任一种可能的设计中所述的方法。
在一个可能的设计中,该装置还包括收发器,用于该装置与其它网元之间进行通信。
在一个可能的设计中,该装置为终端设备。
第七方面,提供一种通信装置,该装置具有实现上述第二方面和第二方面的任一种可能的设计中第一AMF实体行为的功能。所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中,该装置可以是芯片或者集成电路。
在一个可能的设计中,该装置包括存储器和处理器,存储器存储有一组程序,处理器用于执行存储器存储的程序,当程序被执行时,所述装置可以执行上述第二方面和第二方面的任一种可能的设计中所述的方法。
在一个可能的设计中,该装置还包括收发器,用于该装置与其它网元之间进行通信。
在一个可能的设计中,该装置为第一AMF实体。
第八方面,提供一种通信装置,该装置具有实现上述第三方面和第三方面的任一种可 能的设计中第一SMF实体行为的功能。所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中,该装置可以是芯片或者集成电路。
在一个可能的设计中,该装置包括存储器和处理器,存储器存储有一组程序,处理器用于执行存储器存储的程序,当程序被执行时,所述装置可以执行上述第三方面和第三方面的任一种可能的设计中所述的方法。
在一个可能的设计中,该装置还包括收发器,用于该装置与其它网元之间进行通信。
在一个可能的设计中,该装置为第一SMF实体。
第九方面,提供一种通信装置,该装置具有实现上述第四方面和第四方面的任一种可能的设计中第二AMF实体行为的功能。所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中,该装置可以是芯片或者集成电路。
在一个可能的设计中,该装置包括存储器和处理器,存储器存储有一组程序,处理器用于执行存储器存储的程序,当程序被执行时,所述装置可以执行上述第四方面和第四方面的任一种可能的设计中所述的方法。
在一个可能的设计中,该装置还包括收发器,用于该装置与其它网元之间进行通信。
在一个可能的设计中,该装置为第二AMF实体。
第十方面,提供一种通信装置,该装置具有实现上述第五方面和第五方面的任一种可能的设计中第二SMF实体行为的功能。所述功能可以通过硬件实现,也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块。
在一个可能的设计中,该装置可以是芯片或者集成电路。
在一个可能的设计中,该装置包括存储器和处理器,存储器存储有一组程序,处理器用于执行存储器存储的程序,当程序被执行时,所述装置可以执行上述第五方面和第五方面的任一种可能的设计中所述的方法。
在一个可能的设计中,该装置还包括收发器,用于该装置与其它网元之间进行通信。
在一个可能的设计中,该装置为第二SMF实体。
第十一方面,提供一种芯片,该芯片与存储器相连或者该芯片包括存储器,用于读取并执行所述存储器中存储的软件程序,以实现如上述各方面和各方面的任一可能的设计中所述的方法。
第十二方面,提供了一种通信***,该通信***包括第一方面~第五方面中任意两方面或任意两方面以上的方面所述的装置。
第十三方面,提供一种计算机存储介质,存储有计算机程序,该计算机程序包括用于执行上述各方面和各方面的任一可能的设计中方法的指令。
第十四方面,提供了一种计算机程序产品,当计算机读取并执行所述计算机程序产品时,使得计算机执行上述各方面和各方面的任一可能的设计中所述的方法。
图1A和图1B为本申请实施例提供的网络架构;
图2为本申请实施例提供的通信方法的一流程示意图;
图3为本申请实施例提供的通信方法的一流程示意图;
图4为本申请实施例提供的通信方法的一流程示意图;
图5为本申请实施例提供的通信方法的一流程示意图;
图6为本申请实施例提供的通信方法的一流程示意图;
图7为本申请实施例提供的通信方法的一流程示意图;
图8为本申请实施例提供的通信方法的一流程示意图;
图9为本申请实施例提供的通信方法的一流程示意图;
图10为本申请实施例提供的通信装置的一结构示意图;
图11为本申请实施例提供的通信装置的一结构示意图;
图12为本申请实施例提供的终端设备的一结构示意图。
为了便于理解,示例性的给出了与本申请相关概念的说明以供参考,如下所示:
1)终端设备,是一种向用户提供语音和/或数据连通性的设备。具体可以是用户设备(user equipment,UE)、移动台(mobile station,MS)、或移动终端(mobile terminal,MT)等。例如,具有无线连接功能的手持式设备、车载设备等。目前,一些终端的举例为:手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device,MID)、可穿戴设备、虚拟现实(virtual reality,VR)设备、增强现实(augmented reality,AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、或智慧家庭(smart home)中的无线终端等。
2)无线接入网络(radio access network,RAN),可由一个或多个RAN节点组成,比如,5G-RAN节点或未来演进***中的基站。其中,RAN节点可实现无线物理层、资源调度、无线资源管理、无线接入控制以及移动性管理等功能。例如,RAN节点可通过N3接口,与用户面功能(user plane function,UPF)实体相连,用于传输终端设备的数据。再例如,RAN节点可通过N2接口与接入和移动性管理功能(access and mobility management function,AMF)实体相连,用于建立控制面信令连接,实现无线接入承载控制等功能。
3)私网,即企业为了满足企业隐私、通信安全、用户签约管控以及网络资源专享等需求,部署的私有网络。私网的控制面可以包括AMF实体和会话管理功能(session management function,SMF)实体。用户面可以包括UPF实体。可选的,私网还可包括UDM实体、认证服务器功能(authentication server function,AUSF)实体等网元。
4)公网,可为运营商网络。控制面可以包括AMF实体和SMF实体。用户面可以包括UPF实体。可选的,公网还包括UDM实体、AUSF实体、策略控制功能(policy control function,PCF)实体、网络切片选择功能(network slice selection function,NSSF)实体以及网络功能库功能((network function,NF)repository function,NRF)实体等网元。
5)AMF实体,主要负责移动性管理和接入管理等,例如,负责维护和管理终端的状态信息,负责终端的认证,选择网络切片,或选择SMF实体等。具体地,AMF实体,可以用于实现4G***中移动性管理(mobility management entity,MME)实体功能中除会话管理之外的其它功能。
6)SMF实体,主要负责终端设备的会话管理相关的控制面功能,例如,UPF实体的 选择,IP地址的分配,会话的QoS管理,以及从PCF实体获取策略控制和计费(policy control and charging,PCC)策略等。
7)UPF实体,作为PDU会话连接的锚定点,主要负责对终端设备的数据报文过滤、数据传输/转发、速率控制和生成计费信息等。
需要理解的是,在本申请的描述中,“第一”、“第二”等词汇,仅用于区分描述的目的,而不能理解为指示或暗示相对重要性,也不能理解为指示或暗示顺序。
在本申请中,“和/或”,描述关联对象的关联关系,表示可以存在三种关系,例如,A和/或B,可以表示:单独存在A,同时存在A和B,单独存在B的情况,其中A,B可以是单个或者多个。
在本申请中,a、b、或c中的至少一项(个),可以表示:a;b;c;a和b;a和c;b和c;或a、b和c。其中,a、b、c可以是单个,也可以是多个。
下面将结合附图,对本申请实施例的技术方案进行介绍。
如图1A或图1B所示,提供了一种网络架构,利用该网络架构可实现企业私网和运营商公网之间的互联互通。
如图1A或1B所示,在控制面(control plane,CP)上,私网中的AMF实体与公网中的AMF实体之间可以直接进行通信。在用户面(user plane,UP)上,私网中的UPF实体与公网中的UPF实体之间可以直接进行通信。可选的,为了保护公网和私网拓扑的隐私,在图1A所示的网络架构中,公网中的AMF实体与私网中的AMF实体之间可通过CP代理(proxy)服务器进行通信。公网中的UPF实体与私网中的UPF实体之间可通过UP代理服务器进行通信。
利用图1A所示的网络构架,终端设备可从私网归属路由(home-routed)至公网,具体为:终端设备可通过私网的RAN节点,接入至私网AMF实体,通过私网AMF实体与公网AMF实体交互,建立公私网间的协议数据单元(protocol data unit,PDU)会话,该PDU会话至少包括私网UPF实体与公网UPF实体间的数据通道。基于该PDU会话,终端设备可接入到公网,从而可利用公网提供的数据业务。
利用图1B所示的网络架构,终端设备可从公网归属路由至私网,具体为:终端设备可通过公网的RAN节点,接入至公网的AMF实体,通过私网AMF实体与公网AMF实体交互,建立公私网间的PDU会话,该PDU会话至少包括私网UPF实体与公网UPF实体间的数据通道。基于该PDU会话,终端设备可接入至私网,从而利用私网提供的数据业务。
针对图1A和图1B,一种具体示例为:终端设备可首先分别注册到公网与私网中,然后建立公私网间的PDU会话,最后利用该PDU会话接入到公网或私网。可选的,图1A或图1B所示的网络架构还包括数据网络(data network,DN),DN可分别与公网中的UPF实体和私网中的UPF实体相连。
需要说明的是,图1A和图1B所示的网络架构仅作为对本申请所提供的方法或装置的应用网络架构的一种示例,并不作为限定。
如图2所示,本申请实施例提供了一种通信方法,该通信方法可用于建立第一网络与第二网络间的PDU会话。
其中,第一网络可为图1B所示网络架构中的私网,第二网络可为图1B所示网络架构中的公网,或者,第一网络可为图1A所示网络架构中的公网,第二网络可为图1A所示网 络架构中的私网。此外,第二网络可包括第一AMF实体、第一SMF实体和第一UPF实体,第一网络中可包括第二AMF实体、第二SMF实体和第二UPF实体。
如图2所示,该通信流程可具体如下所述。
S201:终端设备生成第一消息。
其中,第一消息可以用于请求建立归属路由到第一网络中的PDU会话,或用于请求建立承载第一网络数据业务的PDU会话。第一消息可以为已有消息,例如,上行非接入层传输(uplink non-access stratum transport,UL NAS TRANSPORT)消息;也可以为新消息,不予限制。
在一个示例中,第一消息用于请求建立归属路由到第一网络中的PDU会话。
进一步地,第一消息中可以包括第一指示信息,第一指示信息可以用于指示上述PDU会话为归属路由到第一网络中的PDU会话。
在另一个示例中,第一消息用于请求建立承载第一网络数据业务的PDU会话。进一步地,第一消息中可以包括第一指示信息,第一指示信息可以用于指示PDU会话为承载第一网络的数据业务的PDU会话。
其中,上述两个示例中的第一指示信息可以包括以下信息中的至少一个:数据网络名(data network name,DNN)、切片选择信息、网络类型指示信息或第一网络的标识信息。
比如,第一指示信息用于指示建立归属路由到公网中的PDU会话,所述网络类型指示信息可具体用于指示公网,所述第一网络的标识信息可具体为公网的标识信息。
其中,公网的标识信息可以用于标识公网,例如,公网的标识信息可以为公共陆地移动网络标识(visit public land mobile network identification,PLMN ID,具体的:PLMN ID可由移动国家码(mobile country code,MCC)和移动网络码(mobile network code,MNC)组成,特定的PLMN ID字段分配给公网,示例性的:***的PLMN为46000,***的PLMN为46001。其中,460为MCC,00/01为MNC。
再比如,第一指示信息用于指示建立归属路由到私网的PDU会话,所述网络类型指示信息可具体用于指示私网,所述第一网络的标识信息可具体为私网的标识信息。
其中,私网的标识信息可以用于标识私网,例如,私网的标识信息可以为PLMN ID,具体的:PLMN ID由MCC和私网移动网络码(private mobile network code,PMNC)组成,特定的PLMN ID字段分配给私网,示例性的:三一重工企业网络的PLMN ID为46056,中国石油企业网络的PLMN ID为46057,其中460为MCC,56/57为PMNC。或者,例如,企业私网的网络标识包含私网指示比特位,用来指示私网,例如,私网网络标识由MCC、私网指示比特位和PMNC组成,示例性的:三一重工企业网络的PLMN ID为460156,中国石油企业网络的PLMN ID为460157,其中460为MCC,1为私网指示比特位,56/57为PMNC。
其中,切片选择信息可为会话管理网络切片选择辅助信息(session management-network slice selection assistance information,S-NSSAI)。
需要说明的是,第一消息中可以不包括第一指示信息,此时,第一消息可以包括数据网络名或切片选择信息中的至少一个,所述数据网络名或切片选择信息可标识第一网络。
可选地,第一消息中包括PDU会话建立请求。
S202:终端设备向第一AMF实体发送所述第一消息。
S203:第一AMF实体根据所述第一消息,向第一SMF实体发送第二消息。
其中,第二消息可以用于请求上述PDU会话的核心网隧道信息,所述核心网隧道信息用于建立第一UPF实体与第二UPF实体之间的数据通道。第二消息可为已有消息,例如,创建PDU会话的上下文请求,也可以为新建消息,不予限制。
在本申请的一示例中,上述第一消息中包括数据网络名和/或切片选择信息,第一AMF实体可根据数据网络名和/或切片选择信息,确定请求建立PDU会话的类型;根据请求建立PDU会话的类型,确定第二指示信息;根据第二指示信息,生成第二消息。其中,第二消息中可以包括第二指示信息。
比如,当所述第一网络为私网且所述第二网络为公网时,所述第二指示信息用于指示所述请求建立的PDU会话的类型为私网;或者,当所述第一网络为公网且所述第二网络为私网时,所述第二指示信息用于指示所述请求建立的PDU会话的类型为公网。
在本申请的一示例中,上述第一消息中可包括第一指示信息。第一AMF实体在接收到第一消息后,可从第一消息中获取第一指示信息,并基于所获取的第一指示信息生成第二消息。其中,第二消息中可以包括第一指示信息。
在本申请的一示例中,上述第一消息中可包括第一指示信息。第一AMF实体在接收到第一消息后,可从第一消息中获取第一指示信息,基于第一指示信息生成第二指示信息,基于第一指示信息和/或第二指示信息生成第二消息。
其中,第二消息中可以包括第一指示信息和/或第二指示信息。
具体地,第一AMF实体可以根据第一指示信息中的数据网络名、切片选择信息、网络类型指示信息和/或第一网络的标识信息,确定请求PDU会话的类型,并根据所述PDU会话的类型,确定第二指示信息。
S204a:第一SMF实体根据第二消息,向第一AMF实体发送第一核心网隧道信息。
其中,第一核心网隧道信息可以用于建立上述PDU会话在第一UPF实体与所述第一网络中UPF实体之间的数据通道。例如,第一核心网隧道信息为PDU会话在第一UPF实体侧的核心网隧道信息。
在一个示例中,第二消息中包括第一指示信息和/或第二指示信息,第一SMF实体根据第一指示信息或第二指示信息,确定第一UPF实体,并为第一UPF实体分配第一核心网隧道信息,向第一AMF实体发送第一核心网隧道信息。
其中,第一SMF实体根据第一指示信息或第二指示信息,确定第一UPF实体可以采用如下两种实现方式。
在一种可能的实现方式中,所述第二指示信息用于指示请求建立PDU会话的类型。进一步地,第一SMF实体可根据上述第二指示信息,确定请求建立PDU会话的类型,并基于请求建立PDU会的类型,在第二网络的UPF实体资源池中选择第一UPF实体,以便通过该第一UPF实体实现第一网络和第二网络网之间的通信。比如,第二网络为公网,第一网络为私网,那么第一SMF实体可在公网的UPF实体资源池中,选择一UPF实体,进一步建立该选择的UPF实体与私网中UPF实体之间的连接,以便用于私网与公网之间进行通信。
在另一种可能的实现方式中,第一消息用于请求建立归属路由到第一网络中的PDU会话。进一步地,第一SMF实体可根据上述第一指示信息中的数据网络名、切片选择信息、网络类型指示信息和/或第一网络的标识信息,确定PDU会话的类型,并基于请求建立PDU会的类型,在第二网络的UPF实体资源池中,选择第一UPF实体,以实现第一网 络和第二网络之间的通信。
在另一个示例中,第一SMF实体可采用现有方法(例如,随机选择,或根据负载选择)选择一个UPF实体作为第一UPF实体,并为该第一UPF实体分配第一核心网隧道信息,向第一AMF实体发送第一核心网隧道信息。
需要说明的是,第一核心网隧道信息可由第一SMF实体分配,也可由第一UPF实体分配,并不作为对本申请的限定。如果第一核心网隧道信息由第一UPF实体分配,由第一UPF实体将第一核心网隧道信息发给第一SMF实体,再由第一SMF实体通过S204a将第一核心网隧道信息发送给第一AMF实体。
可选的,当第一核心网隧道信息是由第一SMF实体分配时,上述方法还包括:S204b:第一SMF实体向第一UPF实体发送第一核心网隧道信息。
S205:第一AMF实体向第二AMF实体发送第一核心网隧道信息。
可选的,上述方法还包括:第一AMF实体向第二AMF实体发送切片选择信息、数据网络名、PDU会话建立请求或第二网络的标识信息中的至少一个。
其中,第二网络的标识信息用于标识第二网络,以通知给第二AMF实体,当前与第二AMF实体进行通信的网络。
需要说明的是,第一核心网隧道信息、切片选择信息、数据网络名、PDU会话建立请求,以及第二网络的标识信息,可携带在同一消息中,也可分别携带在不同的消息中,本申请不作限定。
S206:第二AMF实体向第二SMF实体发送第一核心网隧道信息。
相应的,第二SMF实体接收来自所述第二AMF实体的第二核心网隧道信息。
可选的,上述方法还包括:第二AMF实体向第二SMF实体发送第三指示信息,相应的,第二SMF实体接收来自所述第二AMF实体的第三指示信息。
其中,第三指示信息可用于指示所述PDU会话为从第二网络归属路由到第一网络的PDU会话,或者,用于指示所述PDU会话的访问公共陆地移动网络(visit public land mobile network,VPLMN)为私网类型或公网类型。第三指示信息可以包括第二网络的标识信息。
需要说明的是,第一核心网隧道信息与第三指示信息可携带在同一消息中,也可携带在不同的消息中。
S207a:第二SMF实体向第二AMF实体发送第二核心网隧道信息。
相应的,第二AMF实体接收来自所述第二SMF实体的第二核心网隧道信息。
其中,第二核心网隧道信息可以用于建立所述PDU会话在第一UPF实体与第二UPF实体之间的数据通道。例如,第二核心网隧道信息为PDU会话在第二UPF实体侧的核心网隧道信息。
在一个示例中,当第二AMF实体向第二SMF实体发送第三指示信息时,第二SMF实体可根据第三指示信息确定第二UPF实体,第二SMF实体为第二UPF实体分配第二核心网隧道信息,并向第二AMF实体发送第二核心网隧道信息。
比如,当第一网络为公网,第二网络为私网时,所述第三指示信息可用于指示PDU会话为从私网归属路由到公网的PUD会话,所述第二SMF实体在获得第三指示信息后,可确定当前PDU会话不是本地路由,则可从UPF实体资源池中,选择一第二UPF实体,专门用于和私网进行通信。
在另一个示例中,第二SMF实体可采用现有方法(例如,随机选择,或根据负载选 择)选择一个UPF实体作为第二UPF实体,为第二UPF实体分配第二核心网隧道信息,并向第二AMF实体发送第二核心网隧道信息。
可选的,上述方法还包括:S207b:第二SMF实体向第二UPF实体发送第一核心网隧道信息,或者,第一核心网隧道信息和第二核心网隧道信息。
需要说明的是,第二核心网隧道信息可由第二SMF实体分配,也可由第二UPF实体分配,不予限定。如果第二核心网隧道信息是由第二UPF实体分配的,则由第二UPF实体将第二核心网隧道信息发给第二SMF实体,然后由第二SMF实体通过S207a将第二核心网隧道信息发送给第二AMF实体。此时,S207b中可以仅发送第一核心网隧道信息。
可选的,上述方法还包括:第二SMF实体向第二AMF实体发送PDU会话的QoS参数信息。
相应的,第二AMF实体接收来自所述第二SMF实体的所述PDU会话的QoS参数信息。
其中,QOS参数信息可包括QoS规则(QoS rules)、QoS配置文件(QoS profiles)以及QoS流粒度的QoS参数(QoS flow level QoS parameters)等。
需要指出的是,第二核心网隧道信息与QoS参数信息可携带于同一消息中,也可分别携带于不同的消息中,不作限定。
S208:第二AMF实体向第一AMF实体发送第二核心网隧道信息。
相应的,第一AMF实体接收来自第二AMF实体的第二核心网隧道信息。
可选的,上述方法还包括:第二AMF实体向第一AMF实体发送PDU会话的服务质量(quality of service,QoS)参数信息。
相应的,第一AMF实体接收来自第二AMF实体的PDU会话的QoS参数信息。
其中,第二核心网隧道信息与QoS参数信息可携带在同一消息中,也可分别携带在不同的消息中。
S209:第一AMF实体向第一SMF实体发送第二核心网隧道信息。
相应的,第一SMF实体接收来自第一AMF实体的第二核心网隧道信息。
可选的,上述方法还包括:S210:第一SMF实体向第一UPF实体发送第二核心网隧道信息。
可选的,上述方法还包括:第一AMF实体向第一SMF实体发送所述PDU会话的QoS参数信息。
相应的,第一SMF实体接收来自第一AMF实体的QoS参数信息。
进一步地,第一SMF实体可以根据QoS参数信息,获取所述PDU会话的QoS配置文件和QoS规则。第一SMF实体可向第一AMF实体发送QoS配置文件和QoS规则。相应的,第一AMF实体接收来自第一SMF实体的QoS配置文件和QoS规则,进而第一AMF实体可向RAN节点发送所述QoS配置文件,第一AMF实体可向终端设备发送所述QoS规则。
具体地,QoS参数信息中可包括QoS配置文件和QoS规则。第一SMF实体可在QoS参数信息中,获取QoS配置文件和QoS规则。
可选地,步骤S203中的第二消息具体为创建PDU会话的上下文请求,步骤S204a中的第一核心网隧道信息携带在创建PDU会话的上下文响应中。或者,步骤S203中的第二消息具体为创建PDU会话的上下文请求,步骤S204a中的第一核心网隧道信息携带在N16’ 消息传输请求中。
可选地,步骤S206中的第一核心网隧道信息携带在创建PDU会话的上下文请求中,步骤S207a中的第二核心网隧道信息携带在创建PDU会话的上下文响应中。或者,步骤S206中的第一核心网隧道信息携带在创建PDU会话的上下文请求中,步骤S207a中的第二核心网隧道信息携带在N16’消息传输请求中。
可选的,上述方法还包括:第一AMF实体选择第二SMF实体。进一步地,第二消息中可包括第二SMF实体的标识。
其中,当第一网络为私网时,第二SMF实体为私网中的SMF实体。所述第二SMF实体的标识可具体为私网中SMF实体的标识。
采用上述实施例提供的方法,终端设备向第二网络中的AMF实体请求建立路由到第一网络的PDU会话,第二网络中的AMF实体根据该请求向第二网络中的SMF实体请求PDU会话的第一核心网隧道信息,并向第一网络中的AMF实体发送该第一核心网隧道信息,第一网络中的AMF实体将该第一核心网隧道信息通过第一网络中的SMF实体发送给第一网络中的UPF实体,并从第一网络中的UPF实体获取到该PDU会话的第二核心网隧道信息,进一步将该第二核心网隧道信息通过第二网络中的AMF实体和SMF实体发送给第二网络中的UPF实体,实现了在第一网络中的UPF实体以及第二网络中的UPF实体之间成功建立了PDU会话,即通过两个网络中AMF实体之间的通信接口成功地建立两个网络中UPF实体之间PDU会话,进而解决了公网和私网之间通信问题。
可选地,在上述实施例的一种实施场景下,第一消息中包括数据网络名和/或切片选择信息,上述方法还包括:
第一AMF实体根据数据网络名和/或切片选择信息与指示信息的对应关系,确定与第一消息中的数据网络名和/或切片选择信息所对应的指示信息;
当第一消息中的数据网络名和/或切片选择信息所对应的指示信息用于指示所述PDU会话不允许本地路由时,第一AMF实体确定PDU会话归属路由的网络。
其中,上述对应关系可以为:数据网络名和切片选择信息作为一个组合与指示信息之间的对应关系,或者,数据网络名与指示信息之间的对应关系;或者,切片选择信息与指示信息之间的对应关系。该对应关系可配置在第一AMF实体上,或者,在终端设备的签约数据中。第一AMF实体可在终端设备的签约数据中获取该对应关系。该第一AMF实体可以从UDM实体获取终端设备的签约数据。
此外,指示信息用于指示所述PDU会话是否允许本地路由,具体可以采用通过设置不同的值来不同的含义。例如,指示信息为1,可代表PDU会话不允许本地路由(local breakout)。指示信息为0,可代表PDU会话允许本地路由。
其中,不允许本地路由也可称为归属路由,具体指PDU会话归属路由到终端设备的归属网络。允许本地路由也可称为不归属路由,具体指PDU会话可以通过本地网络进行路由。
其中,上述第一AMF实体确定PDU会话归属路由的网络,可以采用如下方式:
方式一,第一AMF实体根据终端设备的标识,确定所述PDU会话的归属网络为第一网络。
其中,终端设备的标识中可包括公共陆地移动网络(public land mobile network,PLMN)标识,PLMN标识可标识终端设备所归属的运营商公网。例如,当第一网络为公网,第二 网络为私网时,第一AMF实体可根据终端设备的PLMN标识,确定归属路由的运营商公网。例如,移动运营商的网络,或联通运营商的网络,或电信运营商的网络等。
方式二,第一AMF实体根据所述终端设备的签约信息中包括的数据网络名和/或切片选择信息与归属路由网络标识的对应关系,确定所述PDU会话的归属网络为第一网络。
在上述实施例中,通过上述S201和S202,第一AMF实体能够确定终端设备请求建立的PDU会话需要归属路由。通过上述S203和S204b,第一AMF实体能够确定终端设备请求建立的PDU会话在第一UPF实体侧的核心网隧道信息。
但是第一AMF实体并不能确定PDU会话归属路由的网络,通过上述方法,第一AMF实体可具体确定PDU会话需要归属路由的网络。
在4G网络中终端设备漫游的场景中,存在建立终端设备访问网络与终端设备归属网络之间PDU会话的方案,在该方案中,通过访问SMF实体与归属SMF实体之间的通信接口,建立PDU会话。但是在5G网络中,仅在两个网络的AMF实体之间设置有通信接口,两个网络的SMF实体之间并未设置有通信接口。本申请实施例提供的方法,可以用于解决如何利用两个AMF实体之间的通信接口,建立两个网络之间PDU会话的问题。
如图3所示,本申请实施例提供了另一种通信方法。该方法以第二网络为私网,第二网络中的第一AMF实体、第一UPF实体和第一SMF实体分别为访问AMF(visit-AMF,V-AMF)实体、访问UPF(visit-UPF,V-UPF)实体和访问SMF(visit-SMF,V-SMF)实体,第一网络为公网,第一网络中的第二AMF实体、第二UPF实体和第二SMF实体分别为归属AMF(home-AMF,H-AMF)实体、归属UPF(home-UPF,H-UPF)实体和归属SMF(home-SMF,H-SMF)实体,且终端设备为UE为例进行描述,如下所述。
S301:UE向V-AMF实体发送移动性管理非接入层消息(mobile management non-access stratum,MM NAS)消息。
其中,MM NAS消息可为上述图2中第一消息的一种示例。
其中,MM NAS消息可以包括PDU会话建立请求(PDU session establishment request)。例如,MM NAS消息中可包括会话管理(session management,SM)消息,SM消息中可包括PDU会话建立请求。
可选的,MM NAS消息中还包括S-NSSAI,数据网络名DNN、PDU会话标识(PDU Session ID)或公网PDU会话指示(public PDU session indication)中的至少一个。
具体地,MM NAS消息可以为上行非接入层传输(UL NAS TRANSPORT)消息。
其中,PDU会话建立请求中可携带PDU类型(PDU type),业务和会话连续性模式(session and service continuity mode,SSC mode)。PDU类型可指示PUD会话为IPV4类型,或者IPV6类型。业务和会话连续性模式可指示PDU会话的业务和会话连续性模式,比如,PDU会话的业务和会话连续性模式可为mode1、mode2或mode3。mode1指IP地址的锚点(UPF实体)不变,支持业务连续性。mode2指IP地址的锚点(UPF实体)可变,且在为终端设备建立新PDU会话的过程中,网络先释放终端设备的旧PDU会话,然后再通知终端设备建立新的PDU会话。mode3指IP地址的锚点(UPF实体)可变,且在为终端设备建立新PDU会话的过程中,网络先通知终端设备建立新的PDU会话,然后再释放终端设备的旧PDU会话。
S302:V-AMF实体确定为UE建立归属路由的PDU会话。
在一个示例中,V-AMF实体可根据MM NAS消息中的S-NSSAI、数据网络名DNN或公网PDU会话指示中的至少一个,确定为UE建立归属路由的PDU会话,而不建立通过本地网络路由的PDU会话。V-AMF实体可根据S-NSSAI、数据网络名DNN或公网PDU会话指示中的至少一个,确定UE请求建立的PDU会话是否允许本地路由,如果V-AMF实体确定UE请求建立的PDU会话不允许本地路由,则为UE建立归属路由的PDU会话,否则为UE建立本地路由的PDU会话。
S303:V-AMF实体选择V-SMF实体。
示例性地,V-AMF实体可根据网络切片选择辅助信息和/或数据网络名,选择V-SMF实体。
可选的,上述方法还包括:V-AMF实体根据网络切片选择辅助信息和/或数据网络名,选择H-SMF实体。
S304:V-AMF实体向V-SMF实体发送PDU会话创建会话管理上下文请求。
其中,PDU会话创建会话管理上下文请求可为网元SMF的PDU会话创建会话管理上下文请求(Nsmf_PDUSession_Create SM Context Request)。PDU会话创建会话管理上下文请求可具体为上述图2中的第二消息的一示例。
可选的,PDU会话创建会话管理上下文请求中携带有公网PDU会话指示(public PDU session indication)。
S305:V-SMF实体选择V-UPF实体。
可选的,V-SMF实体基于PDU会话创建会话管理上下文请求中携带的公网PDU会话指示,在私网的UPF实体资源池中选择一个UPF实体,通过该UPF实体可实现与公网之间的通信。
S306:V-SMF实体建立N4会话。
其中,N4会话的建立过程可包括:V-SMF实体向V-UPF实体发送请求消息,V-UPF实体向V-SMF实体发送该请求消息的响应消息。
其中,访问核心网隧道信息(visit corenetwork,V-CN,tunnel info)可由V-SMF实体分配,也可由V-UPF实体分配,所述访问核心网隧道信息也可称为私网核心网隧道信息。如果访问核心网隧道信息由V-SMF实体分配,则请求消息中可携带有访问核心网隧道信息。如果访问核心网隧道信息由V-UPF实体分配,则响应消息中可携带有访问核心网隧道信息。
S307:V-SMF实体向V-AMF实体发送N16’消息传输请求。
比如,N16’消息传输请求可具体为网元AMF的通信服务的N16’消息传输请求(Namf_communication_N16’message transfer request)。
其中,N16’消息传输请求中可携带有访问核心网隧道信息。所述访问核心网隧道信息可具体为上述图2所示的第一核心网隧道信息的一示例。
可替代的,S307也可为:V-SMF实体向V-AMF实体发送PDU会话创建会话管理上下文响应,例如,PDU会话创建会话管理上下文响应可具体为网元SMF的PDU会话创建会话管理上下文响应(Nsmf_PDU session_CreateSMContext response)。其中,PDU会话创建会话管理上下文响应中携带有访问核心网隧道信息。
S308:V-AMF实体向H-AMF实体发送N14’请求消息。
其中,N14’请求消息中可包括网络切片选择辅助信息、数据网络名、PDU会话建立请求或访问核心网隧道信息中的至少一个。
可选的,N14’请求消息中还包括私网的标识信息。
S309:H-AMF实体向H-SMF实体发送PDU会话创建会话管理上下文请求。
例如,PDU会话创建会话管理上下文响应可具体为网元SMF的PDU会话创建会话管理上下文响应。
其中,PDU会话创建会话管理上下文请求中可包括网络切片选择辅助信息、数据网络名、PDU会话建立请求或访问核心网隧道信息中的一个或多个等。
可选的,PDU会话创建会话管理上下文请求中还包括VPLMN ID。
其中,VPLMN ID可用于指示PDU会话为从私网归属路由到公网的PDU会话,或者,VPLMN ID用于指示PDU会话的类型为私网类型。比如,VPLMN ID中的某些比特位可用于指示VPLMN网络为私网。
需要说明的是,如果N14’请求消息中未包括私网的标识信息,V-AMF实体可根据配置信息识别发送N14’消息的V-AMF实体所在网络的VPLMN ID,从而根据VPLMN ID确定私网的标识信息。
S310:H-SMF实体将所述PDU会话注册到H-UDM实体,并从H-UDM实体获取所述UE的会话管理签约信息。
比如,UE的会话管理签约信息可包括签约永久标识(subscription permanent identifier,SUPI)、NSSAI、或DNN的签约信息等。
S311:H-SMF实体执行PCF会话管理策略关联建立流程(SM Policy Association Establishment procedure)。
其中,H-SMF实体执行PCF会话管理策略关联建立流程,可包括:H-SMF实体从PCF实体获取PDU会话的PCC规则。
需要说明的是,步骤S310和S311均为可选步骤。
S312:H-SMF实体为所述PDU会话建立到H-UPF实体的N4会话。
其中,N4会话的建立过程可包括:H-SMF实体向H-UPF实体发送请求消息,H-UPF实体向H-SMF实体发送该请求消息的响应消息。
其中,归属核心网隧道信息(home corenetwork,H-CN,tunnel info)可由H-SMF实体分配,也可由H-UPF实体分配,归属核心网隧道信息可为上述图2所示流程中的第二核心网隧道信息的一示例。
需要指出的是,如果归属核心网隧道信息由H-SMF实体分配,则请求消息中可携带有归属核心网隧道信息。如果归属核心网隧道信息由H-UPF实体分配,则响应消息中可携带有归属核心网隧道信息。
S313:H-SMF实体向H-AMF实体发送N16’消息传输请求。
其中,H-SMF实体可根据S309步骤中的PDU会话创建会话管理上下文请求中携带的访问核心网隧道信息,确定当前需建立N9隧道(N9 tunnel),而不建立N3隧道(N3 tunnel),进而向H-AMF实体返回N16’消息传输请求。或者,H-SMF实体也可根据S309步骤中的PDU会话创建会话管理上下文请求中携带的VPLMN ID,确定当前需建立N9隧道(N9 tunnel),而不建立N3隧道(N3 tunnel),进而向H-AMF实体返回N16’消息传输请求。
其中,N16’消息传输请求中可包括以下信息中的一个或多个:QoS规则(QoS Rules),协议配置选项(protocol configuration option,PCO,PDU会话选择类型(selected PDU Session type)、SSC模式(SSC mode)、归属核心网隧道信息(H-CN Tunnel Info)、QoS流 标识(QoS flow identifier,QFI)、QoS配置文件(QoS profiles)以及汇聚最大比特率(aggregated maximum bite rate,Session-AMBR)。
可替代的,S313还可为:H-SMF实体向H-AMF实体发送PDU会话创建会话管理上下文响应。其中,PDU会话创建会话管理上下文响应中可包括以下信息中的一个或多个:QoS规则,PCO,PDU会话选择类型、SSC模式、归属核心网隧道信息、QFI(s)、QoS配置文件以及Session-AMBR。
S314:H-AMF实体向V-AMF实体发送N14’消息响应(N14'message response)。
其中,N14’消息响应中可包括QoS规则,PCO,PDU会话选择类型、SSC模式、归属核心网隧道信息、QFI(s)、QoS配置文件以及Session-AMBR中的一个或多个。
在一个示例中,H-AMF实体在通过步骤S313接收到N16’消息传输请求后,可从N16’消息传输请求中获取上述QoS规则,PCO,PDU会话选择类型、SSC模式、归属核心网隧道信息、QFI(s)、QoS配置文件以及Session-AMBR等参数,然后将上述参数携带于N14’消息响应中,并通过在步骤S314中将N14’消息响应发送给V-AMF实体。可选地,上述参数单独作为N14’消息响应中的信元。
在另一个示例中,H-AMF实体通过步骤S313接收到N16’消息传输请求后,可将N16’消息传输请求直接携带于N14’消息响应中,通过步骤S314将所述N14’消息响应发送给V-AMF实体。
S315:V-AMF实体向V-SMF实体发送PDU会话更新会话管理上下文请求。
例如,PDU会话更新会话管理上下文请求可为网元SMF的PDU会话更新会话管理上下文请求(Nsmf_PDU Session_Update SM Context Request)。
其中,PDU会话更新会话管理上下文请求中可包括上述QoS规则,PCO,PDU会话选择类型、SSC模式、归属核心网隧道信息、QFI(s)、QoS配置文件以及Session-AMBR中的一个或多个。
可选的,上述参数也直接携带在PDU会话更新会话管理上下文请求中,也即上述参数可以单独作为PDU会话更新会话管理上下文请求的信元,上述参数由V-AMF实体通过S315发送给V-SMF实体。或者,上述参数可携带于N16’消息传输请求中,N16’消息传输请求可携带于PDU会话更新会话管理上下文请求中,上述参数同样由V-AMF实体通过S315发送给V-SMF实体。
S316:V-SMF实体向V-AMF实体发送N1N2消息传输请求,例如N1N2消息传输请求可为网元AMF的传输服务的N1N2消息传输请求(Namf_communication_N1N2 message transfer request)。
其中,N1N2消息传输请求中可包括PDU会话的参数信息,例如,PDU会话的参数信息可包括发送给UE的N1 SM信息(N1 SM information)和发送给RAN节点的第一N2 SM信息(N2 SM information)。N1 SM信息可包括PDU会话建立接受(PDU Session Establishment Accept)。比如,PDU会话建立接受中可包括认证QoS规则(authorized QoS rule)、SSC mode、S-NSSAI、分配IPV4地址(allocated IPv4 address)以及Session-AMBR等。第一N2 SM信息可包括PDU会话标识、QoS配置文件、核心网隧道信息、S-NSSAI和Session-AMBR等。
S317:V-AMF实体向RAN节点发送N2 PDU会话请求(N2 PDU session request)。
其中,N2 PDU会话请求中可包括N1 SM信息和第一N2 SM信息。
S318:RAN节点和UE进行RRC消息交互。
其中,通过RAN节点和UE的RRC消息交互,可为PDU会话建立空口资源,同时,可将N1 SM信息发给UE。
S319:RAN节点向V-AMF实体回复N2 PDU会话响应(N2 PDU Session Response)。
其中,N2 PDU会话响应中可包括PDU Session ID、原因值Cause和第二N2 SM信息。其中,第二N2 SM信息中可包括PDU Session ID、RAN隧道信息(tunnel Info)和接受/拒绝QoS配置文件列表(list of accepted/rejected QoS profiles)。
S320:V-AMF实体向V-SMF实体发送PDU会话的更新会话管理上下文请求,例如,PDU会话的更新会话管理上下文请求可为网元SMF的PDU会话的更新会话管理上下文请求(Nsmf_PDU session_update SM context request)。
其中,PDU会话更新会话管理上下文请求中可携带有第二N2 SM信息。
S321:V-SMF实体向V-UPF实体发送N4会话修正(N4 session modification)。
其中,N4会话修正中可包括RAN隧道信息。
S322:V-SMF实体向V-AMF实体发送PDU会话更新会话管理上下文响应,例如,PDU会话更新会话管理上下文响应可为网元SMF的PDU会话更新会话管理上下文响应(Nsmf_PDU session_update SM context response)。
在本申请实施例中,UE可通过私网的RAN节点,发送请求建立从私网归属路由到公网的PDU会话至私网AMF实体,私网AMF实体通过可发送请求至公网AMF实体,且私网AMF且为该PDU会话分配私网UPF侧的核心网隧道信息,而公网AMF实体可为该PDU会话分配公网UPF侧的核心网隧道信息,从而建立公私网间的PDU会话。
如图4所示,本申请实施例提供了又一种通信方法,该通信方法可用于修改(modification)第一网络与第二网络间的PDU会话。在该方法中,第一网络可为图1B所示网络架构中的私网,第二网络可为图1B所示网络架构中的公网,或者,第一网络可为图1A所示网络架构中的公网,第二网络可为图1A所示网络架构中的私网,终端设备可以为UE。该方法具体如下所述。
S401:UE生成第一消息。
其中,第一消息用于请求修改归属路由到第一网络中的PDU会话。第一消息可以为已有消息,例如,上行非接入层传输消息;也可以为新消息,不予限制。
S402:UE向第一AMF实体发送第一消息。
其中,第一消息中可包括N1 SM消息。N1 SM消息中可包含PDU会话修改请求(PDU Session Modification Request)。
需要指出的是,S401和S402的执行主体可替换为RAN节点。
S403:第一AMF实体向第二AMF实体发送第二消息。
具体的,第一AMF实体可根据存储的所述PDU会话的信息,判断PDU会话是否为需要归属路由到第一网络的PDU会话,如果是,则向第二AMF实体发送第二消息,所述第二消息,用于请求修改所述PDU会话,所述第二消息包含N1 SM消息。
可选的,在所述PDU会话建立成功后,所述第一AMF实体可将所述PDU会话标记为需要归属路由到第一网络的PDU会话。
S404:第二AMF实体根据所述第二消息,向第二SMF实体发送第三消息。
其中,第三消息包含所述N1 SM消息,所述第三消息用于请求修改所述PDU会话。
可选的,在所述PDU会话建立成功后,第二AMF实体可将所述PDU会话标记为需要归属路由到第一网络的PDU会话。
可选的,第三消息中可包括第二指示信息,第二指示信息用于指示所述PDU会话为从第二网络归属路由到第一网络的PDU会话。
S405a:第二SMF实体根据所述第三消息,向第二AMF实体发送修改后的QoS参数。
其中,修改后的QoS参数用于修改所述PDU会话在第一SMF实体、第一UPF实体、RAN节点和UE至少一个实体上的相应QoS参数。
可选的,在所述PDU会话建立成功后,第二SMF实体可将所述PDU会话标记为需要归属路由到第一网络的PDU会话。
S405b:如果第二SMF实体根据所述第三消息,确定需要修改所述PDU会话在第一UPF实体上的参数,则向第一UPF实体发起N4会话修改流程。
其中,N4会话修改流程用于修改所述PDU会话在第一UPF实体上的参数。
其中,S405a和S405b先后顺序不作限定。此外,步骤S405b为可选步骤。
S406:第二AMF实体向第一AMF实体发送修改后的QoS参数。
S407:第一AMF实体向第一SMF实体发送所述修改后的QoS参数。
S408:如果第一SMF实体根据所述修改的QoS参数,确定需要修改所述PDU会话在第二UPF实体上的参数,则向第二UPF实体发起N4会话修改流程,以修改所述PDU会话在第二UPF实体上的参数。
其中,步骤S408为可选步骤。
在上述实施例中,第一SMF实体可根据所述修改的QoS参数信息,获取所述修改的PDU会话的QoS配置文件和QoS规则,第一SMF实体可向第一AMF实体发送QoS配置文件和QoS规则,第一AMF实体可向RAN节点发送修改的QoS配置文件,第一AMF实体可向UE发送所述修改的QoS规则。
由上可见,可由UE或RAN节点进行触发,修改UE的从私网归属路由到公网的PDU会话。
如图5所示,本申请实施例提供了又一种通信方法,该通信方法可修改第一网络与第二网络间的PDU会话,在该方法中,第一网络可为图1B所示网络架构中的私网,第二网络可为图1B所示网络架构中的公网,或者,第一网络可为图1A所示网络架构中的公网,第二网络可为图1A所示网络架构中的私网,终端设备可以为UE。在本申请实施例中,所述第一网络中还可包括第二UDM实体。在本申请实施例中,可由第二UDM实体触发整个修改流程,或者,由第二UPF实体触发整个修改流程,或者,由第二SMF实体触发整个修改流程,在图5所示的流程中,是以第二SMF实体触发修改流程为例进行说明的,并不作为对本申请的限定。该方法具体如下所述。
S501:第二SMF实体生成修改后的QoS参数,所述修改后的QoS参数用于修改所述PDU会话在第一SMF实体、第一UPF实体、RAN节点和UE至少一个实体上的相应QoS参数。
S502:第二SMF实体向第二AMF实体发送所述修改后的QoS参数。
S503:第二SMF实体根据所述修改后的Qos参数,向第二UPF实体发起N4会话修 改流程,以修改所述PDU会话在第二UPF实体上的参数。其中,S502和S503先后顺序不作限定。
S504:第二AMF实体向第一AMF实体发送所述修改后的QoS参数。
S505:第一AMF实体向第一SMF实体发送所述修改后的QoS参数。
S506:第一SMF实体根据所述修改后的QoS参数,向第一UPF实体发送N4会话修改流程,以修改所述PDU会话在第一UPF实体上的参数。
可选的,所述第一SMF实体可向第一AMF实体发送从所述修改后的QoS参数中获取的QoS profile和/或QoS rule。
在一种实现方式中,所述QoS profile可携带于N2 SM info中,所述QoS rule可携带于N1 SM info中,所述N1 SM info和/或N2 SM info可携带于N1N2消息传输中发送给第一AMF实体。
可选的,第一AMF实体在接收到所述N1N2消息传输后,可将所述N1N2消息传输中的QoS profile发送给RAN节点,和/或,将所述QoS rule发送给UE。
由上可见,在本申请实施例中,可由第二SMF实体、第二UDM实体或第二UPF实体进行触发,修改从私网归属路由到公网的PDU会话。
如图6所示,本申请实施例提供了又一种通信方法。该方法以第二网络为私网,第二网络中的第一AMF实体、第一UPF实体和第一SMF实体分别为V-AMF实体、V-UPF实体和V-SMF实体,第一网络为公网,第一网络中的第二AMF实体、第二UPF实体和第二SMF实体分别为H-AMF实体、H-UPF实体和H-SMF实体,终端设备为UE为例。
在图6所示的通信方法中,可由UE触发对PDU会话的修改,也可由RAN节点触发对PDU会话的修改,也可由H-SMF实体触发对PDU会话的修改。在本实施例中,以选择A(OptionA)、选择B(OptionB)和选择C(OptionC)为例,说明上述三种情况。其中,选项A可包括S601a至S605a,选项B可包括S601b至S604b,选项C可包括S601c和S602c。
选项A,可具体为:
S601a:UE向V-AMF实体发送PDU会话修改请求(PDU session modification request)。
S602a:V-AMF实体根据存储的PDU会话的信息,确定所述PDU需归属路由到公网。
可选的,在所述PDU会话建立成功后,V-AMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
S603a:V-AMF实体向H-AMF实体发送N14’请求消息(N14’message request)。
其中,所述N14’请求消息中包括PDU会话修改请求(PDU session modification request),所述PDU会话修改请求用于修改PDU会话的QoS参数。
S604a:H-AMF实体向H-SMF实体发送PDU会话更新会话管理上下文请求。
例如,所述PDU会话更新会话管理上下文请求可为网元SMF的PDU会话更新会话管理上下文请求(Nsmf_PDU session_update SM context request),所述PDU会话更新会话管理上下文请求中可包括PDU会话修改请求(PDU session modification request)。
可选的,所述PDU会话更新会话管理上下文请求中还可以包括用于指示所述PDU会话从私网归属路由到公网的指示信息。
可选的,在所述PDU会话建立成功后,所述H-AMF实体可将所述PDU会话标记为 从私网归属路由到公网的PDU会话。
S605a:H-SMF实体向H-AMF实体发送PDU会话更新会话管理上下文请求响应。
其中,所述PDU会话更新会话管理上下文请求响应可为网元SMF的PDU会话更新会话管理上下文请求响应(Nsmf_PDU session_update SM context request response),所述PDU会话更新会话管理上下文请求响应中可包括修改后的QoS参数,所述修改后的QoS参数用于修改所述PDU会话在V-SMF实体、V-UPF实体、RAN节点和UE至少一个实体上的相应QoS参数。
可选的,在所述PDU会话建立成功后,所述H-SMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
可替代的,步骤S605a:H-SMF实体向H-AMF实体发送N16’消息传输请求,所述N16’消息传输请求中携带有所述修改后的QoS参数。
选项B,具体为:
S601b:RAN节点向V-AMF实体发送N2消息(N2 message),所述N2消息中可包括N2 SM信息和PDU会话标识等。
S602b:V-AMF实体向H-AMF实体发送N14’消息。
其中,所述N14’消息用于请求修改PDU会话。
其中,所述N14’消息可以包括所述N2 SM信息,或者所述N2 SM信息和PDU会话标识。
可选的,在所述PDU会话建立成功后,所述V-AMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
S603b:H-AMF实体向H-SMF实体发送PDU会话更新会话管理上下文请求(PDU session update SM context request)。
其中,所述PDU会话更新SM上下文请求中包括所述N2 SM信息。
可选的,所述PDU会话更新会话管理上下文请求中还可以包括用于指示所述PDU会话为从私网归属路由到公网的指示信息。
可选的,在所述PDU会话建立成功后,所述H-AMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
S604b:H-SMF实体向H-AMF实体发送PDU会话更新会话管理上下文请求响应(PDU session update SM context request response)。
其中,所述PDU会话更新会话管理上下文请求响应中可包括修改后的QoS参数。所述修改后的QoS参数用于修改所述PDU会话在第一SMF实体、第一UPF实体、RAN节点和UE至少一个实体上的相应QoS参数。
可选的,在所述PDU会话建立成功后,所述H-SMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
可替代的,步骤S604b为:H-SMF实体向H-AMF实体发送N16’消息传输请求,所述N16’消息传输请求中携带有所述修改后的QoS参数。
需要说明的是,N16’消息也可称为N16消息,所述N16和N16’可对应于同一接口,比如两个SMF实体间的接口。N14’消息也可称为N14消息,所述N14和N14’可对应于同一接口,比如两个AMF实体间的接口。
选择C,具体为:
S601c:H-SMF实体生成修改后的QoS参数。
在本申请实施例中,可由H-PCF实体触发整个修改流程,或者可由H-UDM实体触发整个修改流程,或者,由H-SMF实体触发整个修改流程。
S602c:H-SMF实体向H-AMF实体发送修改后的QoS参数,所述修改后的QoS参数用于修改所述PDU会话在第一SMF实体、第一UPF实体、RAN节点和UE至少一个实体上的相应QoS参数。可选的,所述修改后的QoS参数可通过N16’消息传输请求发送给H-AMF实体;或者,所述修改后的QoS参数可通过N1N2消息传输请求发送给H-AMF实体。
可选的,在本申请实施例中,在S605a、S604b或S602c之后,所述方法还可包括:
S606:H-SMF实体与H-UPF实体间进行N4会话修改(N4 session modification)。
其中,所述N4会话修改用于修改所述PDU会话在H-UPF实体上的配置参数。
S607:H-AMF实体向V-AMF实体发送N14’消息响应(N14’message response)。
其中,所述N14’消息响应中可包括修改后的QoS参数。
可选的,所述修改后的QoS参数可以单独作为N14’消息响应的信元,即所述修改后的QoS参数可直接携带于N14’消息响应中,所述修改后的QoS参数可由H-SMF实体通过S605a或S604a或S602c发给H-AMF实体;或者,所述修改后的QoS参数可以携带于N16’消息传输请求中,所述N16’消息可携带于N14’消息中;或者,所述修改后的QoS参数可以携带于N1N2消息传输请求中,所述N1N2消息传输请可携带于N14’消息中。
S608:V-AMF实体向V-SMF实体发送PDU会话更新会话管理上下文请求,所述PDU会话更新会话管理上下文请求中可包括修改后的QoS参数。
可选的,所述修改后的QoS参数可直接携带于PDU会话更新会话管理上下文请求中,即所述修改后的QoS参数可以单独作为所述PDU会话更新SM上下文请求的信元,所述修改后的QoS参数由H-AMF实体通过S607发给H-AMF实体;或者,所述修改后的QoS参数可以携带于N16’消息传输请求中,所述N16’消息传输请求可携带于PDU会话更新会话管理上下文请求中;或者,所述修改后的QoS参数可携带于N1N2消息传输请求中,所述N1N2消息传输请求携带于PDU会话更新会话管理上下文请求中。
S609:V-SMF实体向V-AMF实体发送N1/N2消息传输(N1/N2 message transfer)。
其中,V-SMF实体可从所述修改后的QoS参数中获取QoS profile和/或QoS rule,所述QoS profile可包含在N2 SM info中,所述QoS rule可包含在N1 SM info中,N1 SM info和/或N2 SM info可包含在N1N2消息传输中发送给V-AMF实体。
S610:V-AMF实体向RAN节点发送N2 PDU会话请求。其中,所述N2 PDU会话请求中可包括N1 SM info和/或N2 SM info。
S611:RAN节点与UE间进行RRC重配置。
可选的,如果RAN节点在S6010收到了N1 SM info,则在RRC重配置流程中发送给UE。
S612:RAN节点向V-AMF实体发送N2 PDU会话请求回复(N2 PDU session request ack)。
S613:V-AMF实体向V-SMF实体发送PDU会话更新会话管理上下文请求。
S614:V-SMF实体与V-UPF实体间进行N4会话修改,用于修改V-UPF实体上的配置参数。
由上可见,在本申请实施例中,可修改UE的从私网归属路由到公网的PDU会话。
如图7所示,本申请提供一种通信方法,该通信方法可释放(release)第一网络与第二网络间的PDU会话,比如,在该方法中,第一网络可为图1B所示网络架构中的私网,第二网络可为图1B所示网络架构中的公网,或者,第一网络可为图1A所示网络架构中的公网,第二网络可为图1A所示网络架构中的私网,终端设备可以为UE。如图7所示,该流程具体为:
S701:UE生成第一消息,所述第一消息用于请求释放归属路由到第一网络中的PDU会话。
S702:UE向第一AMF实体发送所述第一消息。
S703:第一AMF实体根据所述第一消息,向第二AMF实体发送第二消息,所述第二消息用于请求释放所述PDU会话。
具体的,所述第一AMF实体可根据存储的所述PDU会话的信息,判断所述PDU会话是否为需要归属路由到第一网络的PDU会话,如果是,则向第二AMF实体发送第二消息,所述第二消息,用于请求释放所述PDU会话。可选的,在本申请实施例中,在所述PDU会话建立成功后,所述V-AMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
可替代的,S701至S703为:第一AMF实体向第二AMF实体发送第二消息。即在本申请实施例中,可直接由第一AMF实体触发归属路由的PDU会话释放。
S704:第二AMF实体根据所述第二消息,向第二SMF实体发送第三消息,所述第三消息用于请求释放所述从私网归属路由到公网的PDU会话。可选的,在所述PDU会话建立成功后,所述第二AMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
S705a:第二SMF实体根据所述第三消息,向第二AMF实体发送释放参数,所述释放参数用于释放所述从私网归属路由到公网的PDU会话。可选的,在所述PDU会话建立成功后,所述第二SMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
S705b:第二SMF实体根据所述第三消息,释放配置在第二UPF实体上的所述PDU会话的配置参数。其中,步骤S705a和S705b先后顺序不作限定。
S706:第二AMF实体向第一AMF实体发送所述释放参数。
S707:第一AMF实体向第一SMF实体发送所述释放参数。
S708:第一SMF实体根据所述释放参数,释放配置在第一UPF实体上的所述PDU会话的配置参数。
在本申请实施例中,所述PDU会话的释放参数中可包括发送给RAN节点的N2接口会话管理资源释放请求(N2 SM Resource Release request)和/或发送给UE的PDU会话释放命令(PDU Session Release Command)。由上可见,在本申请实施例中,可由UE或第一AMF实体进行触发,释放UE的从私网归属路由到公网的PDU会话。
如图8所示,本申请提供一种通信方法,该通信方法可释放(release)第一网络与第二网络间的PDU会话,在该方法中,第一网络可为图1B所示网络架构中的私网,第二网 络可为图1B所示网络架构中的公网,或者,第一网络可为图1A所示网络架构中的公网,第二网络可为图1A所示网络架构中的私网,终端设备可以为UE。
S801:第二SMF实体生成释放参数,所述释放参数用于释放UE的从私网归属路由到公网的PDU会话。可选的,在所述PDU会话建立成功后,所述第二SMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
在本申请实施例中,可由第二PCF实体触发整个释放流程,或者,由第二SMF实体触发整个释放流程,在本申请实施例中以第二SMF实体触发整个释放流程为例进行说明的,并不作为对本申请的限定。如果由第二PCF实体触发整个释放流程,则在步骤S801之前,还可包括第二PCF实体发送触发命令至第二SMF实体。
S802a:第二SMF实体向第二AMF实体发送所述释放参数。
S802b:第二SMF实体根据所述释放参数,释放配置在第二UPF实体上的所述PDU会话的配置参数。其中,S802a和S802b先后顺序不作限定。
S803:第二AMF实体向第一AMF实体发送所述释放参数。可选的,在所述PDU会话建立成功后,所述第二AMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
S804:第一AMF实体向第一SMF实体发送所述释放参数。可选的,在所述PDU会话建立成功后,所述第一AMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
S805:第一SMF实体根据所述释放参数,释放配置在第一UPF实体上的所述PDU会话的配置参数。
由上可见,在本申请实施例中,可由第二SMF实体或第二UPF实体进行触发,释放UE的从私网归属路由到公网的PDU会话。
在本申请实施例中,以第二网络为私网,所述第二网络中的第一AMF实体、第一UPF实体和第一SMF实体分别为V-AMF实体、V-UPF实体和V-SMF实体,所述第一网络为公网,所述第一网络中的第二AMF实体、第二UPF实体和第二SMF实体分别为H-AMF实体、H-UPF实体和H-SMF实体,终端设备为UE为例,如图9所示,本申请提供一种通信方法。在图9所示的通信方法中,可由UE触发对PDU会话的释放,也可由RAN节点触发对PDU会话的释放,也可由H-SMF实体触发对PDU会话的释放。在本申请实施例中,以选择A(OptionA)、选择B(OptionB)和选择C(OptionC)三种情况进行说明。其中,选项A可包括S901a至S904a,选项B可包括S901b至S904b,选项C可包括S901c和S902c。
选择A,具体为:S901a:UE向V-AMF实体发送N1移动管理消息。
其中,所述N1移动管理消息中可包括PDU会话释放请求(PDU session release request)。
S902a:V-AMF实体向H-AMF实体发送N14’消息,所述N14’消息用于请求释放PDU会话。
其中,所述N14’消息中可包括所述PDU会话释放请求。可选的,在所述PDU会话建立成功后,所述V-AMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
S903a:H-AMF实体向H-SMF实体发送PDU会话释放会话管理上下文请求。
例如,PDU会话释放会话管理上下文请求可为网元SMF的PDU会话释放会话管理上下文请求(Nsmf_PDUsession_Release SM context request),所述PDU会话释放会话管理上下文请求中可包括PDU会话释放请求(PDU session release request)等。可选的,在所述PDU会话建立成功后,所述H-AMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
S904a:H-SMF实体向H-AMF实体发送用于释放所述PDU的释放参数。
可选的,所述释放参数可以包含在PDU会话更新会话管理上下文请求响应(PDU session update SM context request response)中;或者,所述释放参数可以包含在N16’消息传输请求中。
可选的,在所述PDU会话建立成功后,所述H-SMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
选项B,可具体为,S901b:V-AMF实体触发PDU会话的释放。
S902b:V-AMF实体向H-AMF实体发送N14’消息,所述N14’消息用于请求释放PDU会话。
可选的,在所述PDU会话建立成功后,所述V-AMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
S903b:H-AMF实体向H-SMF实体发送PDU会话释放会话管理上下文请求。
例如,PDU会话释放会话管理上下文请求可为网元SMF的PDU会话释放会话管理上下文请求(Nsmf_PDUsession_Release SM context request),所述PDU会话释放会话管理上下文请求用于释放所述UE的从私网归属路由到公网的PDU会话。
可选的,在所述PDU会话建立成功后,所述H-AMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
S904b:H-SMF实体向H-AMF实体发送用于释放所述PDU的释放参数。
其中,所述释放参数可用于释放所述UE的从私网归属路由到公网的PDU会话。
可选的,所述释放参数可以包含在PDU会话释放网元管理上下文响应中,所述PDU会话释放网元管理上下文响应可为网元SMF的PDU会话释放网元管理上下文响应(Nsfm_PDUsession_ReleaseSM context response)中;或者,所述释放参数可以包含在N16’消息传输请求中。
可选的,在所述PDU会话建立成功后,所述H-SMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
选项C,可具体为,S901c:H-SMF实体生成释放参数,所述释放参数可用于释放所述UE的从私网归属路由到公网的PDU会话。
其中,可由H-PCF触发整个释放流程,或者,由H-SMF实体触发整个释放流程。
S902c:H-SMF实体向H-AMF实体发送所述释放参数。
可选的,所述释放参数可以包含在N16’消息传输请求中;或者所述释放参数可以包含在N1N2消息传输请求中。可选的,在所述PDU会话建立成功后,所述H-SMF实体可将所述PDU会话标记为从私网归属路由到公网的PDU会话。
可选的,在S904a、S904b或S902c之后,所述方法还可包括:
S906:H-SMF实体与H-UPF实体间进行N4会话释放(N4 session release)。
其中,N4会话释放用于释放配置在H-UPF实体上的所述PDU会话的配置参数。
S907:H-AMF实体向V-AMF实体发送N14’消息响应(N14’message response)。
其中,所述N14’消息响应中可包括所述释放参数。
可选的,所述释放参数可以单独作为N14’消息响应的信元,即所述释放参数可直接携带于N14’消息响应中,所述释放参数由H-AMF实体通过S907发给V-AMF实体;或者,所述释放参数可携带于N16’消息传输请求中,所述N16’消息传输请求携带于N14’消息响应中;或者,所述释放参数可以携带于N1N2消息传输请求中,所述N1N2消息传输请求携带于在N14’消息响应中。
S908:V-AMF实体向V-SMF实体发送PDU会话更新会话管理上下文请求。
其中,所述PDU会话更新会话管理上下文请求中可包括所述释放参数。
可选的,所述释放参数可以单独作为PDU会话更新会话管理上下文请求的信元,即所述释放参数可直接携带于PDU会话更新会话管理上下文请求中;或者,所述释放参数可以携带于N16’消息传输请求中,所述N16’消息传输请求携带于PDU会话更新会话管理上下文请求中;或者,所述释放参数可携带于N1N2消息传输请求中,所述N1N2消息传输请求可携带于PDU会话更新会话管理上下文请求中。
可替代的,S908为:V-AMF实体向V-SMF实体发送PDU会话释放会话管理上下文请求。
其中,所述PDU会话释放会话管理上下文请求中可包括所述释放参数。
可选的,所述释放参数可以单独作为PDU会话释放会话管理上下文请求的信元,所述释放参数可直接携带于PDU会话释放会话管理上下文请求中;或者,所述释放参数可携带于N16’消息传输请求中,所述N16’消息传输请求携带于PDU会话释放会话管理上下文请求中;或者,所述释放参数可携带于N1N2消息传输请求中,所述N1N2消息传输请求携带于PDU会话释放会话管理上下文请求中。
S909:V-SMF实体向V-AMF实体发送用于释放所述PDU会话的释放参数,所述PDU会话的释放参数中可包括发送给RAN节点的N2接口会话管理资源释放请求(N2 SM Resource Release request)和/或发送给UE的PDU会话释放命令(PDU Session Release Command)。其中,可选的,所述释放参数可携带于PDU会话的更新会话管理上下文响应中;或者,所述释放参数可以携带于在N1/N2消息转移(N1/N2 message transfer)中;或者,所述释放参数可以携带于PDU会话释放会话管理上下文响应中。
S9010:V-SMF实体与V-UPF实体间进行N4会话释放,所述N4会话释放用于释放配置在V-UPF实体上的所述PDU会话的配置参数。其中,步骤S909和S9010的先后顺序不做限定。
S9011:V-AMF实体向RAN节点发送N2 PDU会话请求。其中,所述N2 PDU会话请求中可包括N2接口会话管理资源释放请求(N2 SM Resource Release request)和PDU会话释放命令(PDU Session Release Command)。
S9012:RAN节点与UE间进行RRC重配置。
可选的,如果S9011中包含所述PDU会话释放命令(PDU Session Release Command),则RAN节点可在RRC重配置流程中将所述PDU会话释放命令发给UE。
S9013:RAN节点向V-AMF实体发送N2 PDU会话请求回复(N2 PDU session request ack)。
S9014:V-AMF实体向V-SMF实体发送PDU会话更新会话管理上下文请求。
在本申请实施例中,可由UE触发对PDU会话的释放,也可由RAN节点触发对PDU会话的释放,也可由H-SMF实体触发对PDU会话的释放。
基于以上构思,如图10所示,本申请提供一种通信装置1000,该通信装置1000可包括处理单元1001和收发单元1002。
在本申请的一示例中,所述通信装置1000可应用于终端设备或终端设备中的芯片,用于执行图2、图3、图4、图5、图6、图7、图8或图9所示流程中,以终端设备为执行主体的步骤。比如,所述处理单元1001,可用于生成第一消息,所述收发单元1002可用于向第一AMF实体发送所述第一消息。
在本申请的一示例中,所述通信装置1000可应用于第一AMF实体或第一AMF实体中的芯片,用于执行图2、图3、图4、图5、图6、图7、图8或图9所示流程中,以第一AMF实体为执行主体的步骤。比如,收发单元1002可用于接收来自终端设备的第一消息,处理单元1001可用于根据所述第一消息,控制收发单元1002向第一SMF实体发送第二消息,所述第二消息用于请求所述PDU会话的核心网隧道信息;所述收发单元1002可用于接收来自所述第一SMF实体的第一核心网隧道信息,并向第二AMF实体发送所述第一核心网隧道信息,所述第一核心网隧道信息用于建立所述PDU会话在第一用户面功能UPF实体与所述第一网络中UPF实体之间的数据通道;
在本申请的一示例中,所述通信装置1000可应用于第一SMF实体或第一SMF实体中的芯片,用于执行图2、图3、图4、图5、图6、图7、图8或图9所示流程中,以第一SMF实体为执行主体的步骤。比如,收发单元1002可用于接收来自第一接入和移动性管理功能AMF实体的第二消息,所述第二消息用于请求PDU会话的核心网隧道信息;所述收发单元1002可用于向所述第一AMF实体发送第一核心网隧道消息,所述第一核心网隧道信息用于建立所述PDU会话在第一用户面功能UPF实体与第一网络中UPF实体之间的数据通道。
在本申请的一示例中,所述通信装置1000可应用于第二AMF实体或第二AMF实体中的芯片,用于执行图2、图3、图4、图5、图6、图7、图8或图9所示流程中,以第二AMF实体为执行主体的步骤。比如,收发单元1002可用于接收来自第一AMF实体的第一核心网隧道信息,所述第一核心网隧道信息用于建立PDU会话在第一用户面功能UPF实体与第一网络中UPF实体间的数据通道;所述收发单元1002还用于向第二SMF实体发送所述第一核心网隧道信息。
在本申请的一示例中,所述通信装置1000可应用于第二SMF实体或第二SMF实体中的芯片,用于执行图2、图3、图4、图5、图6、图7、图8或图9所示流程中,以第二SMF实体为执行主体的步骤。比如,收发单元1002可用于接收来自第二AMF实体的第一核心网隧道信息,所述第一核心网隧道信息用于建立PDU会话在第一用户面功能UPF实体与第一网络中UPF实体之间的数据通道;收发单元1002可用于向所述第二AMF实体发送第二核心网隧道信息,所述第二核心网隧道信息用于建立所述PDU会话在所述第一UPF实体与第二UPF实体之间的数据通道。
关于处理单元1001和收发单元1002的具体功能,可参见图2、图3、图4、图5、图6、图7、图8或图9所示流程的介绍,在此不再赘述。
基于上述构思,如图11所示,本申请还提供一种通信装置1100,该通信装置1100可 应用于上述图2至图9所示流程中的终端设备或终端设备中的芯片,也可应用于上述图2至图9所示流程中的第一AMF实体或第一AMF实体中的芯片,也可应用于上述图2至图9所示流程中的第一SMF实体或第一SMF实体中的芯片,也可应用于上述图2至图9所示流程中的第二AMF实体或第二AMF实体中的芯片,也可应用于上述图2至图9所示流程中的第二SMF实体或第二SMF实体中的芯片,在此不作限定。
该通信装置1100可包括处理器1101和存储器1102。进一步的,该装置还可包括接收器1104和发送器1105。进一步的,该装置还可包括总线***1103。
其中,处理器1101、存储器1102、接收器1104和发送器1105可通过总线***1103相连,该存储器1102可用存储指令,该处理器1101可用于执行该存储器1102存储的指令,以控制接收器1104接收信号,并控制发送器1105发送信号,完成上述图2至图9所示方法中以终端设备、第一SMF实体、第一AMF实体、第二SMF实体或第二AMF实体为主体的步骤。
其中,接收器1104和发送器1105可以为不同的物理实体,也可为相同的物理实体,可以统称为收发器。存储器1102可以集成在处理器1101中,也可以是与处理器1101不同的物理实体。
作为一种实现方式,接收器1104和发送器1105的功能可以考虑通过收发电路或收发的专用芯片实现。处理器1101可以考虑通过专用处理芯片、处理电路、处理器或通用芯片实现。
作为另一种实现方式,可以考虑使用计算机的方式,来实现本申请实施例提供的网络设备或终端设备的功能。即将实现处理器1101、接收器1104和发送器1105功能的程序代码存储在存储器1102中,通用处理器可通过执行存储器中的代码来实现处理器1101、接收器1104和发送器1105的功能。
该通信装置1100所涉及的与本申请提供的技术方案相关的概念、解释和详细说明以及其他步骤,可参见前述方法或其它实施例中关于这些内容的描述,此处不作赘述。
在本申请的一示例中,该通信装置1100可应用于终端设备或终端设备中的芯片,所述通信装置1100可用于执行上述图2至图9所示流程中,以终端设备为执行主体的步骤。比如,处理器1101,可用于生成第一消息,发送器1105,可用于向第一AMF实体发送第一消息。
在本申请的一示例中,该通信装置1100可应用于第一AMF实体或第一AMF实体中的芯片,所述通信装置1100可用于执行上述图2至图9所示流程中,以第一AMF实体为执行主体的步骤。比如,接收器1104,可用于接收来自终端设备的第一消息,处理器1101可用于根据所述第一消息,控制发送器1105发送第二消息,接收器1104可用于接收来自第一SMF实体的第一核心网隧道信息。
在本申请的一示例中,该通信装置1100可用于第一SMF实体或第一SMF实体中的芯片,所述通信装置1100可用于执行上述图2至图9所示流程中,以第一SMF实体为执行主体的步骤。比如,接收器1104,可用于接收来自第一AMF实体的第二消息,发送器1105可用于向第一AMF实体发送第一核心网隧道消息。
在本申请的一示例中,该通信装置1100可应用于第二AMF实体或第二AMF实体中的芯片,所述通信装置1100可用于执行上述图2至图9所示流程中,以第二AMF实体为执行主体的步骤。比如,接收器1104,可用于接收来自第一AMF实体的第一核心网隧道 信息,所述发送器1105,可用于向第二SMF实体发送第一核心网隧道信息。
在本申请的一示例中,该通信装置1100可应用于第二SMF实体或第二SMF实体中的芯片,所述通信装置1100可用于执行上述图2至图9所示流程中,以第二SMF实体为执行主体的步骤。比如,接收器1104,可用于接收来自第二AMF实体的第一核心网隧道信息,发送器1105,可用于向第二AMF实体发送第二核心网隧道信息。
关于处理器1101、接收器1104以及发送器1105的介绍,可参见上述图2至图9所示流程的介绍,在此不再赘述。
与上述构思相同,图12提供了一种终端设备的结构示意图,该终端设备可适用于图2至图9中所示的流程,以终端设备为执行主体的步骤,为了便于说明,图12仅示出了终端设备的主要部件。如图12所示,终端设备1200可包括处理器、处理器、存储器、控制电路,可选的,还可以包括天线和/或输入输出装置。处理器可用于对通信协议以及通信数据进行处理,以及对用户设备进行控制,执行软件程序,处理软件程序的数据。存储器可以存储软件程序和/或数据。控制电路可用于基带信号与射频信号的转换以及对射频信号的处理。控制电路和天线一起也可以叫做收发器,可用于收发电磁波形式的射频信号。输入输出装置,例如触摸屏、显示屏、键盘等,可用于接收用户输入的数据以及对用户输出数据。
在本申请实施例中,处理器可以读取存储单元中的软件程序,解释并执行软件程序的指令,处理软件程序的数据。当需要通过无线发送数据时,处理器对待发送的数据进行基带处理后,输出基带信号至射频电路,射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到用户设备时,射频电路通过天线接收到射频信号,将射频信号转换为基带信号,并将基带信号输出至处理器,处理器将基带信号转换为数据并对该数据进行处理。
本领域技术人员可以理解,为了便于说明,图12仅示出了一个存储器和处理器。在实际的用户设备中,可以存在多个处理器和存储器。存储器也可以称为存储介质或者存储设备等,本申请实施例对此不做限制。
作为一种可选的实现方式,处理器可以包括基带处理器和中央处理器,基带处理器可用于对通信协议以及通信数据进行处理,中央处理器可用于对整个用户设备进行控制,执行软件程序,处理软件程序的数据。图12中的处理器集成了基带处理器和中央处理器的功能,本领域技术人员可以理解,基带处理器和中央处理器也可以是各自独立的处理器,通过总线等技术互联。本领域技术人员可以理解,终端设备可以包括多个基带处理器以适应不同的网络制式,终端设备可以包括多个中央处理器以增强其处理能力,终端设备的各个部件可以通过各种总线连接。该基带处理器也可以表述为基带处理电路或者基带处理芯片。该中央处理器也可以表述为中央处理电路或者中央处理芯片。对通信协议以及通信数据进行处理的功能可以内置在处理器中,也可以以软件程序的形式存储在存储单元中,由处理器执行软件程序以实现基带处理功能。
示例性的,在本申请实施例中,可以将具有收发功能的天线和控制电路作为终端设备1200的收发单元1201,将具有处理功能的处理器视为终端设备1200的处理单元1202。如图12所示,终端设备1200可包括收发单元1201和处理单元1202。收发单元也可以称为收发器、收发机、收发装置等。可选的,可以将收发单元1201中用于实现接收功能的器件视为接收单元,将收发单元1201中用于实现发送功能的器件视为发送单元,即收发单 元1201包括接收单元和发送单元。示例性的,接收单元也可以称为接收机、接收器、接收电路等,发送单元也可以称为发射机、发射器或发射电路等。
应理解,上述各个装置实施例中网络设备与终端设备和方法实施例中的网络设备或终端设备完全对应,由相应的模块或单元执行相应的步骤,例如发送模块(发射器)方法执行方法实施例中发送的步骤,接收模块(接收器)执行方法实施例中接收的步骤,除发送接收外的其它步骤可以由处理模块(处理器)执行。具体模块的功能可以参考相应的方法实施例。发送模块和接收模块可以组成收发模块,发射器和接收器可以组成收发器,共同实现收发功能;处理器可以为一个或多个。
根据本申请实施例提供的方法,本申请实施例还提供一种通信***,其包括前述的终端设备、第一AMF实体、第一SMF实体、第二AMF实体以及第二SMF实体等。
基于以上实施例,本申请实施例还提供了一种计算机存储介质,该存储介质中存储软件程序,该软件程序在被一个或多个处理器读取并执行时可实现上述任意一个或多个实施例提供的方法。该计算机存储介质可以包括:U盘、移动硬盘、只读存储器、随机存取存储器、磁碟或者光盘等各种可以存储程序代码的介质。
基于以上实施例,本申请实施例还提供了一种芯片,该芯片包括处理器,用于实现上述任意一个或多个实施例所涉及的功能,例如获取或处理上述方法中所涉及的信息或者消息。可选地,该芯片还包括存储器,该存储器,用于存储处理器所执行的程序指令和数据。该芯片,也可以包含芯片和其他分立器件。
应理解,在本申请实施例中,处理器可以是中央处理单元(Central Processing Unit,CPU),该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor,DSP)、专用集成电路(application-specific integrated circuit,ASIC)、现成可编程门阵列(field programmable gate array,FPGA)或者其他可编程逻辑器件、晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器,也可以是任何常规的处理器等。
该存储器可以包括只读存储器和随机存取存储器,并向处理器提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。
该总线***除包括数据总线之外,还可以包括电源总线、控制总线和状态信号总线等。但是为了清楚说明起见,在图中将各种总线都标为总线***。在实现过程中,上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成,或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器,处理器读取存储器中的信息,结合其硬件完成上述方法的步骤。为避免重复,这里不再详细描述。
在本申请的各个实施例中,如果没有特殊说明以及逻辑冲突,不同的实施例之间的术语和/或描述具有一致性、且可以相互引用,不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
可以理解的是,在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分,并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定。
Claims (33)
- 一种通信方法,其特征在于,包括:终端设备生成第一消息,所述第一消息用于请求建立归属路由到第一网络中的协议数据单元PDU会话;所述终端设备向第一接入和移动性管理功能AMF实体发送所述第一消息,所述第一AMF实体为第二网络中的网元。
- 根据权利要求1所述的方法,其特征在于,所述第一消息中包括第一指示信息,所述第一指示信息用于指示所述PDU会话为归属路由到所述第一网络中的PDU会话。
- 根据权利要求2所述的方法,其特征在于,所述第一指示信息包括数据网络名、切片选择信息、网络类型指示信息或所述第一网络的标识信息中的至少一个。
- 根据权利要求1所述的方法,其特征在于,所述第一消息包括数据网络名或切片选择信息中的至少一个。
- 一种通信方法,其特征在于,包括:第一接入和移动性管理功能AMF实体接收来自终端设备的第一消息,所述第一消息用于请求建立归属路由到第一网络的协议数据单元PDU会话;所述第一AMF实体根据所述第一消息,向第一会话管理功能SMF实体发送第二消息,所述第二消息用于请求所述PDU会话的核心网隧道信息;所述第一AMF实体接收来自所述第一SMF实体的第一核心网隧道信息,并向第二AMF实体发送所述第一核心网隧道信息,所述第一核心网隧道信息用于建立所述PDU会话在第一用户面功能UPF实体与所述第一网络中UPF实体之间的数据通道;其中,所述第一AMF实体、所述第一SMF实体和第一用户面功能UPF实体为第二网络中的网元,所述第二AMF实体为所述第一网络中的网元。
- 根据权利要求5所述的方法,其特征在于,所述第一消息包括第一指示信息,所述第一指示信息用于指示所述PDU会话为归属路由到所述第一网络中的PDU会话。
- 根据权利要求6所述的方法,其特征在于,所述第一指示信息包括数据网络名、切片选择信息、网络类型指示信息或所述第一网络的标识信息中的至少一个。
- 根据权利要求6或7所述的方法,其特征在于,所述第二消息包括所述第一指示信息。
- 根据权利要求5所述的方法,其特征在于,所述第一消息中包括数据网络名和/或切片选择信息,所述方法还包括:所述第一AMF实体根据数据网络名和/或切片选择信息与指示信息的对应关系,确定与所述第一消息中的数据网络名和/或切片选择信息所对应的指示信息;当所述第一消息中的数据网络名和/或切片选择信息所对应的指示信息用于指示所述PDU会话不允许本地路由时,所述第一AMF实体根据所述终端设备的标识,确定所述PDU会话的归属网络为所述第一网络,或者,所述第一AMF实体根据所述终端设备的签约信息中包括的数据网络名和/或切片选择信息与归属路由网络标识的对应关系,确定所述PDU会话的归属网络为所述第一网络。
- 根据权利要求5至9任一项所述的方法,其特征在于,所述第二消息中包括第二 指示信息;其中,当所述第一网络为私网且所述第二网络为公网时,所述第二指示信息用于指示所述请求建立的PDU会话的类型为私网类型;或者,当所述第一网络为公网且所述第二网络为私网时,所述第二指示信息用于指示所述请求建立的PDU会话的类型为公网类型。
- 根据权利要求5至10任一项所述的方法,其特征在于,所述方法还包括:所述第一AMF实体选择第二SMF实体,所述第二SMF实***于所述第一网络。
- 根据权利要求11所述的方法,其特征在于,所述第二消息中包括所述第二SMF实体的标识;其中,当所述第一网络为私网时,所述第二SMF实体的标识用于指示所述第二SMF实体为私网中的SMF实体;或者,当所述第一网络为公网时,所述第二SMF实体的标识用于指示所述第二SMF实体为公网中的SMF实体。
- 根据权利要求5至12任一项所述的方法,其特征在于,所述方法还包括:所述第一AMF实体向所述第二AMF实体发送切片选择信息、数据网络名、PDU会话建立请求或所述第二网络的标识信息中的至少一个。
- 根据权利要求5至13任一项所述的方法,其特征在于,所述方法还包括:所述第一AMF实体接收来自所述第二AMF实体的第二核心网隧道信息,所述第二核心网隧道信息用于建立所述PDU会话在所述第一UPF实体与所述第一网络中第二UPF实体之间的数据通道;所述第一AMF实体向所述第一SMF实体发送所述第二核心网隧道信息。
- 根据权利要求14所述的方法,其特征在于,所述方法还包括:所述第一AMF实体接收来自所述第二AMF实体的所述PDU会话的服务质量QoS参数信息;所述第一AMF实体向所述第一SMF实体发送所述PDU会话的QoS参数信息;所述第一AMF实体接收来自所述第一SMF实体的QoS配置文件和QoS规则;所述第一AMF实体向无线接入网设备发送所述QoS配置文件;所述第一AMF实体向终端设备发送所述QoS规则。
- 一种通信方法,其特征在于,包括:第一会话管理功能SMF实体接收来自第一接入和移动性管理功能AMF实体的第二消息,所述第二消息用于请求协议数据单元PDU会话的核心网隧道信息;所述第一SMF实体根据所述第二消息,向所述第一AMF实体发送第一核心网隧道消息,所述第一核心网隧道信息用于建立所述PDU会话在第一用户面功能UPF实体与第一网络中UPF实体之间的数据通道;其中,所述第一AMF实体、所述第一SMF实体和所述第一UPF实体为第二网络中的网元。
- 根据权利要求16所述的方法,其特征在于,所述第二消息中包括第一指示信息;其中,当所述第一网络为私网时,所述第二指示信息用于指示所述请求建立的PDU会话的类型为私网类型;或者,当所述第一网络为公网时,所述第二指示信息用于指示所述请求建立的PDU会话的类型为公网类型。
- 根据权利要求16或17所述的方法,其特征在于,所述第二消息中包括所述第二指示信息,所述第二指示信息用于指示所述PDU会话的类型为私网类型或公网类型。
- 根据权利要求16至18任一项所述的方法,其特征在于,所述第二消息中包括所述第二SMF实体的标识;其中,当所述第一网络为私网时,所述第二SMF实体的标识用于指示所述第二SMF实体为私网中的SMF实体;当所述第一网络为公网时,所述第二SMF实体的标识用于指示所述第二SMF实体为公网中的SMF实体。
- 根据权利要求17至19任一项所述的方法,其特征在于,所述方法还包括:所述第一SMF实体根据所述第一指示信息或所述第二指示信息,确定所述第一UPF实体;所述第一SMF实体为所述第一UPF实体分配所述第一核心网隧道信息;所述第一SMF实体向所述第一UPF实体发送所述第一核心网隧道信息。
- 根据权利要求16至20任一项所述的方法,其特征在于,所述方法还包括:所述第一SMF实体接收来自所述第一AMF实体的第二核心网隧道信息,所述第二核心网隧道信息用于建立所述PDU会话在所述第一UPF实体与所述第一网络中第二UPF实体之间的数据通道;所述第一SMF实体向所述第一UPF实体发送所述第二核心网隧道信息。
- 根据权利要求21所述的方法,其特征在于,所述方法还包括:所述第一SMF实体接收来自所述第一AMF实体的QoS参数信息;所述第一SMF实体根据所述QoS参数信息,获取所述PDU会话的QoS配置文件和QoS规则;所述第一SMF实体向所述第一AMF实体发送所述QoS配置文件和所述QoS规则。
- 一种通信方法,其特征在于,包括:第二接入和移动性管理功能AMF实体接收来自第一AMF实体的第一核心网隧道信息,所述第一核心网隧道信息用于建立协议数据单元PDU会话在第一用户面功能UPF实体与第一网络中UPF实体间的数据通道;所述第二AMF实体向第二会话管理功能SMF实体发送所述第一核心网隧道信息;其中,所述第二AMF实体和所述第二SMF实体为所述第一网络中的网元,所述第一AMF实体和所述第一UPF实体为第二网络中的网元。
- 根据权利要求23所述的方法,其特征在于,所述方法还包括:所述第二AMF实体向所述第二SMF实体发送第三指示信息,所述第三指示信息用于指示所述PDU会话为从所述第二网络归属路由到所述第一网络的PDU会话。
- 根据权利要求24所述的方法,其特征在于,所述第三指示信息中包括所述第二网络的标识信息。
- 根据权利要求23至25任一项所述的方法,其特征在于,所述方法还包括:所述第二AMF实体接收来自所述第二SMF实体的第二核心网隧道信息,所述第二核心网隧道信息用于建立所述PDU会话在所述第一UPF实体和所述第一网络中第二UPF实体间的数据通道;所述第二AMF实体向所述第一AMF实体发送所述第二核心网隧道信息。
- 根据权利要求26所述的方法,其特征在于,所述方法还包括:所述第二AMF实体接收来自所述第二SMF实体的所述PDU会话的QoS参数信息;所述第二AMF实体向所述第一AMF实体发送所述PDU会话的QoS参数信息。
- 一种通信方法,其特征在于,包括:第二会话管理功能SMF实体接收来自第二接入和移动性管理功能AMF实体的第一核心网隧道信息,所述第一核心网隧道信息用于建立协议数据单元PDU会话在第一用户面功能UPF实体与第一网络中UPF实体之间的数据通道;所述第二SMF实体向所述第二AMF实体发送第二核心网隧道信息,所述第二核心网隧道信息用于建立所述PDU会话在所述第一UPF实体与第二UPF实体之间的数据通道;其中,所述第一UPF实体为第二网络中的网元,所述第二AMF实体、所述第二SMF实体和所述第二UPF实体为所述第一网络中的网元。
- 根据权利要求28所述的方法,其特征在于,所述方法还包括:所述第二SMF实体接收来自所述第二AMF实体的第三指示信息;其中,所述第三指示信息用于指示所述PDU会话为从所述第二网络归属路由到所述第一网络的PDU会话。
- 根据权利要求29所述的方法,其特征在于,所述第三指示信息中包括所述第二网络的标识信息。
- 根据权利要求29或30所述的方法,其特征在于,所述方法还包括:所述第二SMF实体根据所述第三指示信息,确定所述第二UPF实体;所述第二SMF实体为所述第二UPF实体分配所述第二核心网隧道信息;所述第二SMF实体向所述第二UPF实体发送所述第二核心网隧道信息。
- 根据权利要求28至31任一项所述的方法,其特征在于,所述方法还包括:所述第二SMF实体向所述第二AMF实体发送QoS参数信息。
- 一种通信装置,其特征在于,包括:存储器,用于存储程序;处理器,用于与所述存储器耦合,调用所述存储器中的程序,执行所述程序以实现如权利要求1至32任意一项所述的方法。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP19864342.1A EP3849251B1 (en) | 2018-09-30 | 2019-09-09 | Communication method and apparatus |
US17/217,434 US11844142B2 (en) | 2018-09-30 | 2021-03-30 | Communications method and apparatus |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201811161320.XA CN110972218B (zh) | 2018-09-30 | 2018-09-30 | 一种通信方法及装置 |
CN201811161320.X | 2018-09-30 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US17/217,434 Continuation US11844142B2 (en) | 2018-09-30 | 2021-03-30 | Communications method and apparatus |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020063317A1 true WO2020063317A1 (zh) | 2020-04-02 |
Family
ID=69950012
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2019/104968 WO2020063317A1 (zh) | 2018-09-30 | 2019-09-09 | 一种通信方法及装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US11844142B2 (zh) |
EP (1) | EP3849251B1 (zh) |
CN (1) | CN110972218B (zh) |
WO (1) | WO2020063317A1 (zh) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220330019A1 (en) * | 2020-03-31 | 2022-10-13 | Zte Corporation | Parameters for application communication establishment |
Families Citing this family (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113709904B (zh) * | 2020-05-22 | 2024-04-09 | 华为技术有限公司 | 连接建立的方法、装置和*** |
WO2021248275A1 (en) * | 2020-06-08 | 2021-12-16 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for network interworking |
CN113810950A (zh) * | 2020-06-15 | 2021-12-17 | 华为技术有限公司 | 一种通信方法及装置 |
CN113938880B (zh) * | 2020-06-29 | 2024-05-14 | 华为技术有限公司 | 一种应用的验证方法及装置 |
CN114449590B (zh) * | 2020-10-16 | 2023-08-18 | 大唐移动通信设备有限公司 | 会话创建方法及装置 |
CN114500164A (zh) * | 2020-11-11 | 2022-05-13 | ***通信有限公司研究院 | Vlan的实现方法、核心网设备及终端 |
CN112511403A (zh) * | 2020-12-14 | 2021-03-16 | 深圳艾灵网络有限公司 | 一种虚拟局域网通信方法、设备及存储介质 |
CN113115468B (zh) * | 2021-02-26 | 2023-02-03 | 深圳艾灵网络有限公司 | 5g本地网络的控制方法及装置、服务器、***和存储介质 |
CN113115473B (zh) * | 2021-03-01 | 2022-09-30 | 深圳艾灵网络有限公司 | 网络切片控制方法及装置、服务器、***及存储介质 |
CN113225836B (zh) * | 2021-04-30 | 2022-02-01 | 广州爱浦路网络技术有限公司 | 低轨卫星与5g核心网的通信方法、***、装置及存储介质 |
CN115484595A (zh) * | 2021-05-31 | 2022-12-16 | 华为技术有限公司 | 一种公私网业务的隔离方法、装置及*** |
CN115515082B (zh) * | 2021-06-21 | 2023-11-24 | 普天信息技术有限公司 | 一种4g、5g公专网融合集群通信方法及*** |
KR20230050048A (ko) * | 2021-10-07 | 2023-04-14 | 삼성전자주식회사 | 무선 통신 시스템에서 Home Routed 세션의 Visited 사업자 망에서 세션 분기 방법 및 장치 |
CN116074801A (zh) * | 2021-10-29 | 2023-05-05 | 华为技术有限公司 | 通信***、通信方法和通信装置 |
WO2023133871A1 (zh) * | 2022-01-17 | 2023-07-20 | 华为技术有限公司 | 通信方法和装置 |
CN114640981B (zh) * | 2022-02-16 | 2023-08-01 | 南方科技大学 | 处理5g核心网巨链接的优化方法及装置、设备 |
CN115002852A (zh) * | 2022-04-27 | 2022-09-02 | 中国电信股份有限公司 | 网络接入方法、装置、电子设备及可读存储介质 |
CN117062145A (zh) * | 2022-05-05 | 2023-11-14 | 华为技术有限公司 | 一种QoS控制方法和对应装置 |
CN114900792A (zh) * | 2022-06-14 | 2022-08-12 | 中国联合网络通信集团有限公司 | 通信方法、终端、基站设备、园区通信***及存储介质 |
CN118175530A (zh) * | 2022-12-08 | 2024-06-11 | 维沃移动通信有限公司 | 通信方法、终端及核心网功能 |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108323245A (zh) * | 2017-06-19 | 2018-07-24 | 华为技术有限公司 | 一种注册及会话建立的方法、终端和amf实体 |
Family Cites Families (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2018111029A1 (ko) * | 2016-12-15 | 2018-06-21 | 엘지전자(주) | 무선 통신 시스템에서 핸드오버 수행 방법 및 이를 위한 장치 |
CN108401269A (zh) * | 2017-02-07 | 2018-08-14 | 中兴通讯股份有限公司 | 跨***的切换方法和装置 |
CN108401271B (zh) * | 2017-02-07 | 2021-03-26 | 中兴通讯股份有限公司 | 基站的切换方法、***及存储介质 |
US10251147B2 (en) * | 2017-03-20 | 2019-04-02 | Samsung Electronics Co., Ltd. | Method for supporting efficient PDU session activation and deactivation in cellular networks |
EP3818777A1 (en) * | 2018-07-06 | 2021-05-12 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and devices for connecting a wireless communication device to a user plane in a wireless communication network |
CN110536375B (zh) * | 2018-08-09 | 2022-07-15 | 中兴通讯股份有限公司 | 网络接入方法、装置、网络设备和计算机可读存储介质 |
US11539427B2 (en) * | 2019-10-03 | 2022-12-27 | Qualcomm Incorporated | Delay management in wireless networks |
US20230108625A1 (en) * | 2021-09-27 | 2023-04-06 | Cable Television Laboratories, Inc. | Enhanced multi-access protocol data unit (pdu) session |
US11777795B2 (en) * | 2021-09-30 | 2023-10-03 | Cisco Technology, Inc. | Local breakout of user plan function at enterprise 5G radio access network |
US11910299B2 (en) * | 2021-10-05 | 2024-02-20 | Cisco Technology, Inc. | Providing slice attribute information to user equipment in a mobile network environment |
-
2018
- 2018-09-30 CN CN201811161320.XA patent/CN110972218B/zh active Active
-
2019
- 2019-09-09 EP EP19864342.1A patent/EP3849251B1/en active Active
- 2019-09-09 WO PCT/CN2019/104968 patent/WO2020063317A1/zh unknown
-
2021
- 2021-03-30 US US17/217,434 patent/US11844142B2/en active Active
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN108323245A (zh) * | 2017-06-19 | 2018-07-24 | 华为技术有限公司 | 一种注册及会话建立的方法、终端和amf实体 |
Non-Patent Citations (3)
Title |
---|
"3GPP Technical Specification Group Services and System Aspects; Study on the security aspects of the next generation system (Release 14)", 3GPP TR 33.899 V1.3.0, 31 August 2017 (2017-08-31), XP051336126 * |
ERICSSON: "OI 4c: Handover and slicing", SA WG2 MEETING #123 S2-176981, 27 October 2017 (2017-10-27), XP051346937 * |
HUAWEI ET AL: "SMF selection in roaming case", SA WG2 MEETING #122 S2-174542, XP051303387 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20220330019A1 (en) * | 2020-03-31 | 2022-10-13 | Zte Corporation | Parameters for application communication establishment |
Also Published As
Publication number | Publication date |
---|---|
CN110972218B (zh) | 2021-04-09 |
EP3849251A1 (en) | 2021-07-14 |
US11844142B2 (en) | 2023-12-12 |
EP3849251B1 (en) | 2023-11-08 |
CN110972218A (zh) | 2020-04-07 |
US20210219124A1 (en) | 2021-07-15 |
EP3849251A4 (en) | 2021-11-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2020063317A1 (zh) | 一种通信方法及装置 | |
KR102436804B1 (ko) | 세션 관리 방법, 장치 및 시스템 | |
EP3592033A1 (en) | Communication method and device | |
KR102469973B1 (ko) | 통신 방법 및 장치 | |
WO2021208861A1 (zh) | 授权方法、策略控制功能设备和接入和移动管理功能设备 | |
EP4044630A1 (en) | Communication method, apparatus, and device | |
CN114071574B (zh) | QoS流控制方法及通信装置 | |
CN114079995A (zh) | 一种中继管理方法及通信装置 | |
CN113873478A (zh) | 通信方法及装置 | |
EP4271043A1 (en) | Communication method, apparatus and system | |
WO2019174582A1 (zh) | 一种消息传输方法和装置 | |
CN113873443B (zh) | 通信方法及装置 | |
CN114513864A (zh) | 多路径传输方法和通信装置 | |
EP4181542A1 (en) | Proximity service communication method, management network element, terminal device, and communication system | |
EP4207828A1 (en) | Data communication method and communication apparatus | |
EP4408057A1 (en) | Communication method and apparatus | |
WO2023236764A1 (zh) | 一种分配互联网协议地址的方法及通信装置 | |
CN114902609B (zh) | 一种通信方法、设备、***及存储介质 | |
WO2024051313A1 (zh) | 通信资源管理方法、装置、***及存储介质 | |
WO2024032041A1 (zh) | 通信方法和通信装置 | |
EP4262244A1 (en) | Method and device for determining mec access point | |
WO2024027299A1 (zh) | 消息路由方法和装置 | |
WO2023065990A1 (zh) | 一种通信方法及装置 | |
CN117596584A (zh) | 通信方法和通信装置 | |
WO2018202105A1 (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: 19864342 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2019864342 Country of ref document: EP Effective date: 20210408 |