WO2024012230A1 - Procédé et appareil de communication - Google Patents

Procédé et appareil de communication Download PDF

Info

Publication number
WO2024012230A1
WO2024012230A1 PCT/CN2023/104208 CN2023104208W WO2024012230A1 WO 2024012230 A1 WO2024012230 A1 WO 2024012230A1 CN 2023104208 W CN2023104208 W CN 2023104208W WO 2024012230 A1 WO2024012230 A1 WO 2024012230A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
slice identifier
identifier
access
network element
Prior art date
Application number
PCT/CN2023/104208
Other languages
English (en)
Chinese (zh)
Inventor
陈泽昊
李永翠
倪慧
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024012230A1 publication Critical patent/WO2024012230A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • 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

Definitions

  • the present application relates to the field of communication, and in particular, to a communication method and device.
  • edge computing (EC) services often have relatively high latency requirements, so multi-access edge computing (MEC) platforms need to be deployed intensively.
  • MEC multi-access edge computing
  • a reasonable way is for multiple operators (or third parties) to jointly deploy the MEC platform, that is, edge hosting environment (EHE).
  • EHE edge hosting environment
  • a MEC platform with a specific function or a specific service may be deployed by different operators in different locations, or the service may be deployed only on MEC platforms deployed by some operators, or the MEC platform may be deployed by only some operators.
  • Carrier deployment may be used to jointly deploy the MEC platform.
  • Embodiments of the present application provide a communication method and device, so that a terminal accessing a home network can still access services deployed on other operator networks.
  • the first aspect is to provide a communication method.
  • the method includes: an access and mobility management network element receives a session establishment request message from a terminal.
  • the access and mobility management network element is deployed in the first network, the first network is the home network of the terminal, and the terminal accesses the home network.
  • the session establishment request message includes a slice identifier associated with the first service deployed on the second network, which is a network other than the home network.
  • the access and mobility management network element determines the second session management network element in the second network based on the slice identifier.
  • the second session management network element is used to establish a session for the terminal to access the first service.
  • the access and mobility management network element of the home network can be based on the slice identifier associated with the first service.
  • Select a second session management network element in the second network so that the second session management network element can establish a session of the first service for the terminal such as selecting a session anchor point of the first service in the second network, such as a protocol data unit session anchor
  • Click the PSA so that the terminal can access the first service through the PSA, so that the terminal accessing the home network can still access services deployed on other operator networks.
  • the slice identifier associated with the first service is the first slice identifier of the first service in the home network
  • the access and mobility management network element determines the second session in the second network based on the slice identifier.
  • the management network element includes: the access and mobility management network element determines the second session management network element in the second network according to the first slice identifier of the first service in the home network, so as to ensure that the second session management network element The element can support the slice corresponding to the first service.
  • the access and mobility management network element determines the second session management network element according to the first slice identifier, including: the access and mobility management network element determines that the first service is in the first session according to the first slice identifier.
  • the second slice identifier of the second network and the identifier of the second network are used, and the second session management network element is determined based on the second slice identifier and the identifier of the second network.
  • the slice identifier of a certain service in other networks may be the same as the second slice identifier, that is, the second slice identifier is a non-unique identifier, so access and mobility
  • the management network element can use the identifier of the second network to distinguish these same slice identifiers to ensure that the second session management network element within the second network can be selected instead of the session management network element of other networks.
  • the access and mobility management network element determines, according to the first slice identifier, the first service in the second slice of the second network.
  • the identifier, as well as the identifier of the second network includes: the access and mobility management network element determines the second slice identifier and the identifier of the second network based on the first slice identifier and the association relationship.
  • the association relationship is an association relationship between the first slice identifier, the second slice identifier and the identifier of the second network, which is used to facilitate the determination of the second slice identifier and the identifier of the second network associated with the first slice identifier.
  • the access and mobility management network element determines the second session management network element according to the first slice identifier, including: the access and mobility management network element determines that the first service is in the first session according to the first slice identifier. obtain a second slice identifier of the network, and determine the second session management network element based on the second slice identifier. It can be understood that if there is no service in other networks (networks other than the first network and the second network) whose slice identifier is the same as the second slice identifier, that is, the second identifier is a unique identifier, access and mobility management When the network element selects the second session management network element, the identifier of the second network may not be considered, so that the processing logic is simpler.
  • the access and mobility management network element determines the second slice identity of the first service in the second network based on the first slice identity, including: the access and mobility management network element determines the second slice identity of the first service based on the first slice identity, and The association relationship is to determine the second slice identifier, where the association relationship is the association relationship between the first slice identifier and the second slice identifier, to facilitate the determination of the second slice identifier associated with the first slice identifier.
  • the method described in the first aspect may further include: the access and mobility management network element determines the second session management network element.
  • All slice lists contain the first slice identifier.
  • the slice identifier in the first slice list is the slice identifier of the home network of the service deployed by the second network.
  • the access and mobility management network element can determine that the slice identifier is the slice identifier that maps services deployed in other networks to the home network, so that the session management network element located in the other network can be correctly selected.
  • the method described in the first aspect may further include: the access and mobility management network element determines the first session management network element in the home network according to the first slice identifier, and the first session management network element is available Establishing a user plane connection from the terminal to the PSA of the second network to ensure that the terminal can access the first service through the PSA.
  • the method described in the first aspect may further include: the access and mobility management network element sends the first slice identifier to the terminal , to ensure that the terminal can subsequently feed back the first slice identifier.
  • the first slice identifier sent by the access and mobility management network element to the terminal can be carried in the routing policy URSP of the terminal, that is, carried in the existing information element to reduce the difficulty of implementation, or it can also be carried In the new cell, in order to improve the flexibility of implementation, no restrictions are made.
  • the slice identifier associated with the first service is the second slice identifier of the first service in the second network
  • the access and mobility management network element determines the second slice identifier in the second network based on the slice identifier.
  • the session management network element includes: the access and mobility management network element determines the second session management network element according to the second slice identifier and the identifier of the second network.
  • the access and mobility management network element can use the identifier of the second network to distinguish these same slice identifiers to ensure that the second session management network element in the second network can be selected instead of the session management network element of other networks.
  • the slice identifier associated with the first service is the second slice identifier of the first service in the second network
  • the access and mobility management network element determines the second slice identifier in the second network based on the slice identifier.
  • the session management network element includes: the access and mobility management network element determines the second session management network element according to the second slice identifier. That is, if the second slice identifier is a unique identifier, the access and mobility management network element may not consider the identifier of the second network when selecting the second session management network element, so that the processing logic is simpler.
  • the method described in the first aspect further includes: the access and mobility management network element determines that the second slice list contains the second slice logo.
  • the slice identifier in the second slice list is the slice identifier of the service deployed in the second network in the second network.
  • the access and mobility management network element can determine that the slice identifier is the slice identifier of the service deployed in other networks in order to correctly select the session management network element located in the other network.
  • the method described in the first aspect further includes: the access and mobility management network element determines the first session management network element in the home network according to the second slice identifier, and the first session management network element can be used to establish The user plane connection between the terminal and the PSA of the second network ensures that the terminal can access the first service through the PSA.
  • the access and mobility management network element determines the first session management network element in the home network according to the second slice identifier, It includes: the access and mobility management network element determines the first slice identifier of the first service in the home network based on the second slice identifier and the identifier of the second network, thereby determining the first session management based on the first slice identifier. network element. That is, if the second slice identifier is a non-unique identifier, the access and mobility management network element can use the identifier of the second network to distinguish these same slice identifiers to ensure that the first slice identifier can be finally determined. rather than the slice identifier of other networks.
  • the access and mobility management network element determines the first slice identifier of the first service in the home network according to the second slice identifier and the identifier of the second network, including: the access and mobility management network element determines the first slice identifier of the home network according to the second slice identifier.
  • the second slice identifier, the identifier of the second network, and the association relationship determine the first slice identifier.
  • the association relationship is the association relationship between the first slice identifier, the second slice identifier and the identifier of the second network, which is used to facilitate the determination of the first slice identifier associated with the second slice identifier and the identifier of the second network.
  • the access and mobility management network element determines the first session management network element in the home network based on the second slice identifier, including: the access and mobility management network element determines where the first service is based on the second slice identifier.
  • the first slice identifier of the home network thereby determining the first session management network element based on the first slice identifier. That is, if the second slice identifier is a unique identifier, the access and mobility management network element may not consider the identifier of the second network when determining the first slice identifier, which may simplify the processing logic.
  • the access and mobility management network element determines the first slice identifier of the first service in the home network based on the second slice identifier, including: the access and mobility management network element determines the first slice identifier based on the second slice identifier, and the association relationship , determine the first slice identifier.
  • the association relationship is the association relationship between the first slice identifier and the second slice identifier, which is used to conveniently determine the first slice identifier associated with the second slice identifier.
  • the method described in the first aspect further includes: the access and mobility management network element sends the second slice identifier to the terminal to Ensure that the terminal can subsequently feed back the second slice identifier.
  • the second slice identifier sent by the access and mobility management network element to the terminal can be carried in the URSP of the terminal, that is, carried in existing cells to reduce the complexity of solution implementation, or can also be carried in a new In the cell, in order to improve the flexibility of solution implementation, there is no limit.
  • the slice identifier associated with the first service includes the first slice identifier of the first service in the home network, and the second slice identifier of the first service in the second network.
  • the access and mobility management network The element determines the second session management network element in the second network according to the slice identifier, including: the access and mobility management network element determines the first session management network element in the home network according to the first slice identifier, and according to the first slice identifier.
  • the second slice identifier and the identifier of the second network determine the second session management network element.
  • the second session management network element can be used to select the PSA of the first service in the second network, and the first session management network element can be used to establish a user plane connection from the terminal to the PSA to ensure that the terminal can access the first service through the PSA.
  • the method described in the first aspect further includes: the access and mobility management network element sends the association relationship and the first session to the terminal.
  • the association relationship is an association relationship between the first slice identifier, the second slice identifier, and the identifier of the second network.
  • the terminal can implement the process of determining the second slice identifier. For example, the terminal determines the second slice identifier based on the association relationship, the first slice identifier, and the identifier of the second network, thereby simplifying access and mobility management network elements. The implementation complexity is reduced and the overhead on the network side is reduced.
  • the first slice identifier and the identifier of the second network sent by the access and mobility management network element to the terminal can be carried in the URSP of the terminal, that is, carried in existing information elements to reduce implementation difficulty, or It can also be carried in new cells to improve implementation flexibility without limitation.
  • the method described in the first aspect further includes: the access and mobility management network element sends the association relationship and the second slice to the terminal.
  • the association relationship is an association relationship between the first slice identifier, the second slice identifier, and the identifier of the second network.
  • the terminal can implement the process of determining the first slice identifier. For example, the terminal determines the first slice identifier based on the association relationship, the second slice identifier, and the identifier of the second network, thereby simplifying the access and mobility management network. It reduces the implementation complexity of elements and reduces the overhead on the network side.
  • the second slice identifier and the identifier of the second network sent by the access and mobility management network element to the terminal can be carried in the URSP of the terminal, that is, carried in the existing information element to reduce the difficulty of implementation, or also It can be carried in new cells to improve implementation flexibility and is not limited.
  • the slice identifier associated with the first service includes the first slice identifier of the first service in the home network, and the second slice identifier of the first service in the second network.
  • the access and mobility management network The element determines the second session management network element in the second network according to the slice identifier, including: the access and mobility management network element determines the third session management network element in the home network according to the first slice identifier.
  • a session management network element, and determining the second session management network element according to the second slice identifier may not consider the identifier of the second network when determining the second session management network element, so that the processing logic is simpler.
  • the method described in the first aspect further includes: the access and mobility management network element sends the association relationship and the first message to the terminal.
  • Film logo is the association relationship between the first slice identifier and the second slice identifier. That is, if the second slice identifier is a unique identifier, the access and mobility management network element may not provide an association between the network and the slice identifier, so as to save overhead and improve communication efficiency.
  • the first slice identifier sent by the access and mobility management network element to the terminal can be carried in the URSP of the terminal, that is, carried in the existing information element to reduce the difficulty of implementation, or it can also be carried in a new In the cell, in order to improve the flexibility of implementation, there is no limit.
  • the method described in the first aspect further includes: the access and mobility management network element sends the association relationship and the second slice to the terminal. logo.
  • the association relationship is the association relationship between the first slice identifier and the second slice identifier. That is, if the second slice identifier is a unique identifier, the access and mobility management network element may not provide an association between the network and the slice identifier, so as to save overhead and improve communication efficiency.
  • the second slice identifier sent by the access and mobility management network element to the terminal can be carried in the URSP of the terminal, that is, carried in the existing information element to reduce the difficulty of implementation, or it can also be carried in a new information element. Yuanzhong, in order to improve the flexibility of implementation, without any restrictions.
  • the method described in the first aspect further includes: the access and mobility management network element obtains the association relationship from the policy control network element or the network slice selection network element, or may also obtain the association relationship from any other possible network element. , without limitation.
  • the first service is a service that needs to be accessed through the session anchor point of the second network. This can further realize that when the service does not support PSA access of other operators, other operators, such as Terminals in the home network can still access the service.
  • the second aspect is to provide a communication method.
  • the method includes: the terminal sends a session establishment request message to the access and mobility management network element.
  • the access and mobility management network element is deployed on the first network
  • the first network is the home network of the terminal
  • the terminal accesses the home network
  • the session establishment request message includes a slice identifier associated with the first service deployed on the second network
  • the second network is a network other than the home network.
  • the terminal receives the session establishment accept message from the access and mobility management network element, where the session establishment accept message is used to indicate that the second network has established a session for the terminal to access the first service.
  • the slice identifier associated with the first service is the first slice identifier of the first service in the home network.
  • the second aspect The method further includes: the terminal receiving the first slice identifier from the access and mobility management network element.
  • the first slice identifier received by the terminal from the access and mobility management network element is carried in the URSP of the terminal.
  • the slice identifier associated with the first service is the second slice identifier of the first service in the second network.
  • the second aspect The method further includes: the terminal receiving the second slice identifier from the access and mobility management network element.
  • the second slice identifier received by the terminal from the access and mobility management network element is carried in the URSP of the terminal.
  • the slice identifier associated with the first service includes the first slice identifier of the first service in the home network, and the second slice identifier of the first service in the second network.
  • the method described in the second aspect further includes: the terminal may determine the second slice identifier based on the first slice identifier, the identifier of the second network, and the association relationship.
  • the association relationship is an association relationship between the first slice identifier, the second slice identifier and the identifier of the second network.
  • the method in the second aspect further includes: the terminal receives a message from the access and mobility management network.
  • the slice identifier of a certain service in other networks may be the same as the second slice identifier, that is, the second slice identifier is a non-unique identifier, so access and mobility
  • the sexual management network element may provide the terminal with the identifier of the second network to distinguish these same slice identifiers to ensure that the terminal can finally determine the second slice identifier instead of the slice identifiers of other networks.
  • the first slice identifier and the identifier of the second network received by the terminal from the access and mobility management network element are carried in the URSP of the terminal.
  • the slice identifier associated with the first service includes the first slice identifier of the first service in the home network, and the second slice identifier of the first service in the second network.
  • the method described in the second aspect further includes: the terminal may determine the second slice identifier based on the first slice identifier and the identifier of the second network.
  • the association relationship is an association relationship between the first slice identifier, the second slice identifier and the identifier of the second network.
  • the method in the second aspect further includes: the terminal receives an association relationship from the access and mobility management network element and the first slice identifier.
  • the first slice identifier received by the terminal from the access and mobility management network element is carried in the URSP of the terminal.
  • the sexual management network element may not provide an association between the network and the slice identifier, so that the terminal may not consider the identifier of the second network when determining the second slice identifier, thereby making the processing logic simpler.
  • the slice identifier associated with the first service includes the first slice identifier of the first service in the home network, and the second slice identifier of the first service in the second network.
  • the method described in the second aspect further includes: the terminal may determine the first slice identifier based on the second slice identifier, the identifier of the second network, and the association relationship.
  • the association relationship is an association relationship between the first slice identifier, the second slice identifier and the identifier of the second network.
  • the method in the second aspect further includes: the terminal receives a message from the access and mobility management network.
  • the association relationship of the element, the second slice identifier and the identifier of the second network is not limited to:
  • the second slice identifier and the identifier of the second network received by the terminal from the access and mobility management network element are carried in the URSP of the terminal.
  • the slice identifier of a certain service in other networks may be the same as the second slice identifier, that is, the second slice identifier is a non-unique identifier, so access and mobility
  • the sexual management network element may provide the terminal with the identifier of the second network to distinguish these same slice identifiers to ensure that the terminal can finally determine the first slice identifier rather than the slice identifiers of other networks.
  • the slice identifier associated with the first service includes the first slice identifier of the first service in the home network, and the second slice identifier of the first service in the second network.
  • the method described in the second aspect further includes: the terminal may determine the first slice identifier based on the second slice identifier and the association relationship.
  • the association relationship is the first slice identifier and the second slice identifier.
  • the method in the second aspect further includes: the terminal receives the association relationship and the second slice identifier from the access and mobility management network element. slice identifier,
  • the second slice identifier received by the terminal from the access and mobility management network element is carried in the URSP of the terminal.
  • the sexual management network element may not provide an association between the network and the slice identifier, so that the terminal may not consider the identifier of the first network when determining the first slice identifier, thereby making the processing logic simpler.
  • a communication device in a third aspect, includes modules for performing the method described in the first aspect, for example, a transceiver module and a processing module.
  • the transceiver module can be used to realize the function of the device to send and receive messages.
  • the processing module can be used to implement functions of the device other than sending and receiving messages.
  • the transceiver module may include a sending module and a receiving module.
  • the sending module is used to implement the sending function of the communication device described in the third aspect
  • the receiving module is used to implement the receiving function of the communication device described in the third aspect.
  • the communication device described in the third aspect may further include a storage module that stores programs or instructions.
  • the processing module executes the program or instruction
  • the communication device can execute the communication method described in the first aspect.
  • the communication device described in the third aspect may be a network device, such as the first network element, or may be a chip (system) or other component or component that can be disposed in the network device, or may include a network device. device, this application does not limit this.
  • a fourth aspect provides a communication device.
  • the device includes modules for performing the method described in the second aspect, for example, a transceiver module and a processing module.
  • the transceiver module can be used to realize the function of the device to send and receive messages.
  • the processing module can be used to implement functions of the device other than sending and receiving messages.
  • the transceiver module may include a sending module and a receiving module.
  • the sending module is used to implement the sending function of the communication device described in the fourth aspect
  • the receiving module is used to implement the receiving function of the communication device described in the fourth aspect.
  • the communication device described in the fourth aspect may further include a storage module that stores programs or instructions.
  • the processing module executes the program or instruction
  • the communication device can execute the communication method described in the second aspect.
  • the communication device described in the fourth aspect may be a network device, such as an application function, or it may be a chip (system) or other component or component that can be installed in the network device, or it may be a device including a network device. , this application does not limit this.
  • a communication device in a fifth aspect, includes: a processor configured to execute the communication method described in the first aspect or the second aspect.
  • the communication device described in the fifth aspect may further include a transceiver.
  • the transceiver can be a transceiver circuit or an interface circuit.
  • the transceiver can be used for the communication device described in the fifth aspect to communicate with other communication devices.
  • the communication device described in the fifth aspect may further include a memory.
  • This memory can be integrated with the processor or provided separately.
  • the memory may be used to store computer programs and/or data involved in the communication method described in the first aspect or the second aspect.
  • the communication device described in the fifth aspect may be a network device, or may be a chip (system) or other component or component disposed in the network device, or a device including the network device.
  • the technical effects of the communication device described in the fifth aspect may be referred to the technical effects of the communication method described in the first aspect or the second aspect, and will not be described again here.
  • a sixth aspect provides a communication device.
  • the communication device includes: a processor coupled with a memory, and the processor is used to execute a computer program stored in the memory, so that the communication device performs the communication method described in the first aspect or the second aspect.
  • the communication device described in the sixth aspect may further include a transceiver.
  • the transceiver can be a transceiver circuit or an interface circuit.
  • the transceiver can be used for the communication device described in the sixth aspect to communicate with other communication devices.
  • the communication device described in the sixth aspect may be a network device, or may be a chip (system) or other component or component disposed in the network device, or a device including the network device.
  • a seventh aspect provides a communication device, including: a processor and a memory; the memory is used to store a computer program, and when the processor executes the computer program, the communication device executes the first aspect or the second aspect. the communication method described above.
  • the communication device described in the seventh aspect may further include a transceiver.
  • the transceiver can be a transceiver circuit or an interface circuit.
  • the transceiver can be used for the communication device described in the seventh aspect to communicate with other communication devices.
  • the communication device described in the seventh aspect may be a network device, or a chip (system) or other component or component that may be disposed in the network device, or a device including the network device.
  • the technical effects of the communication device described in the seventh aspect may be referred to the technical effects of the communication method described in the first aspect or the second aspect, and will not be described again here.
  • a communication device including: a processor; the processor is configured to be coupled to a memory, and after reading the computer program in the memory, execute the method described in the first aspect or the second aspect according to the computer program. Communication methods.
  • the communication device described in the eighth aspect may further include a transceiver.
  • the transceiver can be a transceiver circuit or an interface circuit.
  • the transceiver can be used for the communication device described in the eighth aspect to communicate with other communication devices.
  • the communication device described in the eighth aspect may be a network device, or a chip (system) or other component or component that may be disposed in the network device, or a device including the network device.
  • a ninth aspect provides a communication system.
  • the communication system includes the first network element described in the first aspect, and/or the application function described in the second aspect.
  • a computer-readable storage medium including: a computer program or instructions; when the computer program or instructions are run on a computer, the computer is caused to execute the communication method described in the first aspect or the second aspect.
  • a computer program product which includes a computer program or instructions.
  • the computer program or instructions When the computer program or instructions are run on a computer, the computer is caused to execute the communication method described in the first aspect or the second aspect.
  • Figure 1 is a schematic diagram of the non-roaming architecture of the 5G system
  • Figure 2 is a schematic diagram of the roaming architecture of the 5G system
  • Figure 3 is a schematic diagram of the scene of the MEC platform
  • Figure 4 is an architectural schematic diagram of a communication system provided by the implementation of this application.
  • Figure 5 is a schematic flow chart 1 of a communication method implemented in this application.
  • Figure 6 is a schematic flow chart 2 of a communication method implemented in this application.
  • Figure 7 is a schematic flow chart 3 of a communication method implemented in this application.
  • Figure 8 is a schematic flow chart 4 of a communication method implemented in this application.
  • Figure 9 is a schematic flow chart 5 of a communication method implemented in this application.
  • Figure 10 is a schematic structural diagram of a communication device provided by the implementation of this application.
  • Figure 11 is a schematic structural diagram 2 of a communication device provided by the implementation of this application.
  • 5G system 5G system, 5GS
  • FIG. 1 is a schematic diagram of the non-roaming architecture of 5GS.
  • 5GS includes: access network (AN) and core network (core network, CN), and can also include: terminals.
  • the above-mentioned terminal may be a terminal with a transceiver function, or a chip or chip system that can be installed on the terminal.
  • the terminal can also be called user equipment (UE), access terminal, subscriber unit (subscriber unit), user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, User terminal, terminal, wireless communication device, user agent or user device.
  • UE user equipment
  • MS subscriber unit
  • MS mobile station
  • remote station remote terminal
  • mobile device User terminal, terminal, wireless communication device, user agent or user device.
  • the terminal in the embodiment of the present application may be a mobile phone (mobile phone), cellular phone (cellular phone), smart phone (smart phone), tablet computer (Pad), wireless data card, personal digital assistant computer (personal digital assistant, PDA) ), wireless modems, handheld devices, laptop computers, machine type communication (MTC) terminals, computers with wireless transceiver functions, virtual reality (VR) Terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, smart grids Wireless terminals in grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, vehicle-mounted terminals, roadside units with terminal functions (road side unit, RSU) etc.
  • the terminal of this application may also be a vehicle-mounted module, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip, or vehicle-mounted unit built into the vehicle as one or more components or units.
  • the above-mentioned AN is used to implement access-related functions. It can provide network access functions for authorized users in specific areas, and can determine transmission links of different qualities to transmit user data according to user levels, business needs, etc.
  • the AN forwards control signals and user data between the terminal and the CN.
  • AN may include: access network equipment, which may also be called radio access network equipment (radio access network, RAN) equipment.
  • RAN radio access network equipment
  • CN is mainly responsible for maintaining mobile network subscription data and providing session management, mobility management, and policies for terminals. Management and security authentication and other functions.
  • CN mainly includes the following: user plane function (UPF), authentication server function (AUSF), access and mobility management function (AMF), session management function (session management function (SMF), network slice selection function (NSSF), network exposure function (NEF), network repository function (NRF), policy control function (PCF) ), unified data management (UDM), unified data repository (UDR), and application function (AF).
  • UPF user plane function
  • AUSF authentication server function
  • AMF access and mobility management function
  • SMF session management function
  • NSSF network slice selection function
  • NEF network exposure function
  • NRF network repository function
  • PCF policy control function
  • UDM unified data management
  • UDR application function
  • AF application function
  • the UE accesses the 5G network through the RAN device.
  • the UE communicates with the AMF through the N1 interface (referred to as N1); the RAN communicates with the AMF through the N2 interface (referred to as N2); the RAN communicates with the UPF through the N3 interface (referred to as N3); SMF It communicates with UPF through the N4 interface (N4 for short), and UPF accesses the data network (DN) through the N6 interface (N6 for short).
  • control plane functions such as AUSF, AMF, SMF, NSSF, NEF, NRF, PCF, UDM, UDR or AF shown in Figure 1 use service-based interfaces for interaction.
  • the external service interface provided by AUSF is Nausf; the external service interface provided by AMF is Namf; the external service interface provided by SMF is Nsmf; the external service interface provided by NSSF is Nnssf; the external service interface provided by NEF is Nnef; the external service interface provided by NRF is Nnrf; the external service interface provided by PCF is Npcf; the external service interface provided by UDM is Nudm; the external service interface provided by UDR is Nudr; the external service interface provided by AF is Naf.
  • RAN equipment may be equipment that provides access to terminals.
  • RAN equipment may include: next-generation mobile communication systems, such as 6G access network equipment, such as 6G base stations, or in the next-generation mobile communication system, the network equipment may also have other naming methods, which are all covered by this application Within the protection scope of the embodiments, this application does not impose any limitations on this.
  • the RAN equipment may also include 5G, such as gNB in the new radio (NR) system, or one or a group (including multiple antenna panels) antenna panels of the base station in 5G, or may also be composed of gNB, transmission point (transmission and reception point, TRP or transmission point, TP) or transmission measurement function (TMF) network node, such as baseband unit (building base band unit, BBU), or centralized unit (centralized unit (CU) or distributed unit (DU), RSU with base station function, or wired access gateway, or 5G core network.
  • 5G such as gNB in the new radio (NR) system, or one or a group (including multiple antenna panels) antenna panels of the base station in 5G, or may also be composed of gNB, transmission point (transmission and reception point, TRP or transmission point, TP) or transmission measurement function (TMF) network node, such as baseband unit (building base band unit, BBU), or centralized unit (centralized unit (CU) or distributed unit (DU), RSU with base station function, or wire
  • RAN equipment can also include access points (APs) in wireless fidelity (WiFi) systems, wireless relay nodes, wireless backhaul nodes, various forms of macro base stations, micro base stations (also (called small stations), relay stations, access points, wearable devices, vehicle-mounted devices, etc.
  • APs access points
  • WiFi wireless fidelity
  • wireless relay nodes wireless backhaul nodes
  • various forms of macro base stations such as, but not limited to, WiFi
  • micro base stations also (called small stations)
  • relay stations such as access points, wearable devices, vehicle-mounted devices, etc.
  • UPF is mainly responsible for user data processing (forwarding, receiving, billing, etc.).
  • UPF can receive user data from a data network (DN) and forward the user data to the terminal through the access network device.
  • UPF can also receive user data from the terminal through the access network equipment and forward the user data to the DN.
  • DN refers to the operator network that provides data transmission services to users.
  • IP Internet protocol
  • multimedia service IP multi-media service, IMS
  • the DN can be an operator's external network or a network controlled by the operator, used to provide business services to terminal devices.
  • PDU protocol data unit
  • the UPF directly connected to the DN through N6 is also called the protocol data unit session anchor (PSA).
  • PDA protocol data unit session anchor
  • AUSF is mainly used to perform security authentication of terminals.
  • AMF is mainly used for mobility management in mobile networks. For example, user location update, user registration network, user switching, etc.
  • SMF is mainly used for session management in mobile networks. For example, session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users, selecting UPF that provides packet forwarding functions, etc.
  • IP Internet Protocol
  • PCF mainly supports providing a unified policy framework to control network behavior, provides policy rules to the control layer network functions, and is responsible for obtaining user subscription information related to policy decisions.
  • PCF can provide policies to AMF and SMF, such as quality of service (QoS) policies, slice selection policies, etc.
  • QoS quality of service
  • NSSF is mainly used to select network slices for terminals.
  • NEF is mainly used to support the opening of capabilities and events.
  • UDM is mainly used to store user data, such as contract data, authentication/authorization data, etc.
  • UDR is mainly used to store structured data.
  • the stored content includes contract data and policy data, externally exposed structured data and application-related data.
  • AF mainly supports interaction with CN to provide services, such as affecting data routing decisions, policy control functions or providing services to the network side. Some services provided by third parties.
  • FIG. 2 is a schematic diagram of the roaming architecture of 5GS.
  • the 5G network includes HPLMN and VPLMN.
  • HPLMN is the home network of the UE
  • VPLMN is the roaming network of the UE.
  • VPLMN and HPLMN communicate through vSEPP and hSEPP.
  • the service can be deployed in HPLMN, that is, the DN is in HPLMN (not shown in the figure), and the terminal communicates with the DN by establishing a home route session.
  • the service can also be located in V-PLMN, that is, the DN is in V-PLMN, and the terminal establishes a local session to communicate with the DN of V-PLMN.
  • an intermediate UPF can be inserted into the session so that the terminal can access services in the data network located in the V-PLMN.
  • TS technical specification, technical standard
  • the UE accesses the 5G network through the RAN device.
  • the UE communicates with the AMF through the N1 interface (referred to as N1); the RAN device communicates with the AMF through the N2 interface (referred to as N2); the RAN device communicates with the AMF through the N3 interface (referred to as N2).
  • N3 for short) communicates with UPF; SMF communicates with UPF through N4 interface (N4 for short).
  • N6 interface referred to as N6
  • UPF communicates with the SMF through the N4 interface (referred to as N4).
  • control plane functions such as NSSF, NEF, AMF, SMF, NRF, or PCF of VPLMN shown in Figure 2 use service-based interfaces for interaction.
  • the external service interface provided by AMF is Namf
  • the external service interface provided by SMF is Nsmf
  • the external service interface provided by NSSF is Nnssf
  • the external service interface provided by NEF is Nnef
  • the external service interface provided by NRF is Nnrf
  • the service interface provided by PCF to the outside world is Npcf.
  • HPLMN's UDM, AUSF, PCF, NRF, NSSF, AF, or NEF control plane functions shown in Figure 2 also use service-based interfaces for interaction.
  • the service-oriented interface provided by AUSF to the outside world is Nausf
  • the service-oriented interface provided by UDM to the outside world is Nudm
  • the service-oriented interface provided by AF to the outside world is Naf.
  • the "Nxx" between the two shown in Figure 2 indicates the interface between the two, and the specific examples will not be given one by one.
  • Network slicing is a key technology for 5G networks driven by demand and technology.
  • 5G networks need to support multi-dimensional logical isolation of services, functions, security, transmission, operation and maintenance based on hardware resource sharing.
  • NFV network functions virtualization
  • SDN software-defined networking
  • Dynamic configuration and efficient scheduling provide powerful technical support. Based on the above reasons, in order to provide mutually isolated network environments for different application scenarios on a unified network infrastructure, and to flexibly customize network functions and characteristics according to their respective needs to ensure the quality of service (QoS) requirements of different businesses, Network slicing came into being.
  • QoS quality of service
  • a network slice can be identified by a single network slice selection assistance information (S-NSSAI), and multiple network slices can be identified by a network slice selection assistance information (NSSAI), that is, a set of S- Collection of NSSAI to identify.
  • S-NSSAI network slice selection assistance information
  • NSSAI network slice selection assistance information
  • the UE needs to complete registration with one or more network slices.
  • the AMF network element can carry the authentication information corresponding to the one or more network slices, such as Allowed NSSAI, in the registration acceptance message sent to the UE to instruct the UE to register to the one or more network slices. , that is, the UE can use this one or more network slices.
  • the AMF network element can determine the Allowed NSSAI based on the UE subscription information obtained from the UDM network element/UDR network element, or obtain the Allowed NSSAI from the NSSF network element, without limitation.
  • Each protocol data unit (PDU) session of the UE can be associated with one S-NSSAI, and the S-NSSAI is one of the Allowed NSSAIs of the UE.
  • the S-NSSAI is one of the Allowed NSSAIs of the UE.
  • the UE can obtain the S-NSSAI corresponding to the service based on the UE route selection policy (UE route selection policy, URSP), and determine whether to use the existing PDU session or establish a new PDU session. If an existing PDU session is used, it means that the S-NSSAI has been associated with the PDU session. If a new PDU session is to be established, the UE needs to verify whether the S-NSSAI is in the Allowed NSSAI. At this time, if the verification is successful, the UE can include the S-NSSAI in the session establishment request to ensure that the subsequently established PDU session, that is, the new PDU session is associated with the S-NSSAI.
  • UE route selection policy UE route selection policy
  • user plane devices basically follow a tree topology deployment. That is, uplink user packets pass through the base station and backhaul network, and finally access the data network through centrally deployed anchor gateways. These anchor gateways are generally deployed at higher locations in the network, such as regional central computer rooms.
  • This topology is relatively simple and facilitates operators to conduct centralized service management and control and packet processing at the anchor point. With the explosive growth of mobile business traffic, this deployment method has become increasingly difficult to support this rapidly growing mobile business traffic model.
  • 5G proposes the concept of EC.
  • EC realizes local processing of distributed business traffic, avoids excessive concentration of traffic, and greatly reduces the impact on the core.
  • it shortens the distance of the backhaul network and reduces the end-to-end (E2E) delay and jitter of user messages, making it possible to deploy ultra-low-latency services.
  • E2E end-to-end
  • the specific implementation of EC is usually a relatively dense deployment of multi-access edge computing (MEC) platforms.
  • MEC multi-access edge computing
  • MEC platform that is, edge hosting environment (EHE).
  • EHE edge hosting environment
  • a MEC platform with a specific function or a specific service may be deployed by different operators in different locations, or the service may be deployed only on MEC platforms deployed by some operators, or the MEC platform may be deployed by only some operators. Carrier deployment.
  • the UE belongs to operator A.
  • the current location of the UE covers both operator A's public land mobile network (PLMN) A, operator B's PLMN B, and service X. It is locally deployed on the MEC platform deployed by operator B.
  • Service X is not deployed on the MEC platform of operator A, or there is no MEC platform deployed by operator B at all. In this scenario, the MEC platform of service X may be deployed, or the server of service X may only allow access to the PSA of operator B.
  • PLMN public land mobile network
  • PLMN B public land mobile network
  • service X is not deployed on the MEC platform of operator A, or there is no MEC platform deployed by operator B at all.
  • the MEC platform of service X may be deployed, or the server of service X may only allow access to the PSA of operator B.
  • PLMN A the UE will access PLMN A and thus cannot access service X through the PSA of PLMNB, which may result in limited access to service X by the
  • the embodiments of this application propose the following technical solutions to solve the problem that terminal access may be restricted because the MEC platform deploying a certain service does not support PSA access of other operators.
  • WiFi wireless fidelity
  • V2X vehicle to everything
  • D2D device-to-device
  • 4G such as long term evolution (LTE) system
  • WiMAX global interoperability for microwave access
  • 5G such as new radio (NR) system
  • future communication systems wait.
  • FIG. 4 is a schematic architectural diagram of a communication system to which the communication method provided by the embodiment of the present application is applicable.
  • this communication system can be applied to the above-mentioned 5G system, mainly including: UE, network elements in network 1, such as UPF, AMF, SMF1, PCF, NSSF, AF, and network elements in network 2, such as SMF2, PSA, EASDF.
  • network elements in network 1 such as UPF, AMF, SMF1, PCF, NSSF, AF
  • network elements in network 2 such as SMF2, PSA, EASDF.
  • the UE accesses network 1, and network 1 is the home network of the UE, that is, the home public land mobile network (HPLMN).
  • HPLMN usually refers to the home operator of the UE or the operator deployed by the UE contract.
  • PLMN usually refers to the home operator of the UE or the operator deployed by the UE contract.
  • PLMN usually refers to the home operator of the UE or the operator deployed by the UE contract.
  • PLMN PLMN.
  • the UE is a China Mobile mobile phone card
  • the UE's home operator is China Mobile
  • the UE's HPLMN is the PLMN deployed by China Mobile.
  • Network 2 and Network 1 are different PLMNs, such as PLMNs deployed by different operators, or Network 2 is a network other than Network 1.
  • Network 1 and Network 2 may be related.
  • Network 2 is a contracted network of Network 1.
  • Network 1 can usually obtain relevant information from Network 2, such as SMF2 information.
  • network 1 and network 2 may not be related.
  • network 2 is not a contracted network of network 1, which is not limited.
  • Network 2 may also be referred to as the non-HPLMN of the UE.
  • Network 2 deploys service 1 of the MEC platform.
  • This service 1 may be limited to PSA access through network 2, or service 1 may be limited to PSA access through the PLMN where service 1 is deployed. That is, service 1 may not be able to pass through.
  • This property of business 1 can also be called X property (or specific property, or any other possible expression).
  • Network 2 can be understood as a PLMN other than the home PLMN, which can be called a non-home PLMN, or a PLMN other than the home PLMN that deploys EC/MEC services, and the EC/MEC services do not support the home PLMN.
  • UPF access, or a PLMN other than the home PLMN that can access the EC/MEC service, and the EC/MEC service does not support UPF access from the home PLMN.
  • AMF can obtain in advance the single network slice selection assistance information (S-NSSAI) associated with the service 1.
  • S-NSSAI single network slice selection assistance information
  • AMF can find SMF1 and SMF2 based on the S-NSSAI associated with service 1.
  • SMF1 can select UPF for the UE
  • SMF2 can select PSA for the UE.
  • SMF1 and SMF2 can establish a user plane connection so that the UE can access the PSA through the UPF to realize access to service 1, thereby solving the problem that the MEC platform deploying service 1 does not support PSA access of other operators, which may cause the UE to have limited access. question.
  • the existing standards do not clearly define visited public land mobile network (VPLMN).
  • the architecture covered by the existing standards involves 5G networks deployed by two different operators, both of which are roaming scenarios, that is, scenarios where UE accesses non-HPLMN. Therefore, in existing standards, in scenarios involving non-HPLMN, the non-HPLMN must be the VPLMN accessed by the UE.
  • the UE accesses an HPLMN, that is, network 1; therefore, a non-HPLMN, that is, network 2, may not be understood as a VPLMN in the usual sense.
  • the network 2 may also be called a VPLMN, or a visited PLMN, without limitation.
  • the network 1 mentioned below can also be understood as the first network
  • the network 2 can also be understood as the second network
  • the service 1 can also be understood as the first service
  • the UE can also be understood as a terminal.
  • Access and The mobility management network element can also be understood as AMF
  • the first session management network element can also be understood as SMF1
  • the second session management network element can also be understood as SMF2
  • the policy control network element can also be understood as PCF
  • the network slicing selection network element can also be understood It can be understood as NSSF, etc.
  • other nouns such as the first slice identifier and S-NSSAI#1, the second slice identifier and S-NSSAI#2, etc., can also be understood similarly, so I won’t go into details one by one. .
  • FIG. 5 is a schematic flowchart 1 of the communication method provided by the embodiment of the present application.
  • the S-NSSAI associated with service 1 may be S-NSSAI#1 of service 1 in network 1.
  • the AMF can determine SMF1 based on S-NSSAI#1, and S-NSSAI#2 of service 1 in network 2, and determine SMF2 based on S-NSSAI#2.
  • SMF1 and SMF2 can establish a user plane connection, so that the UE can access service 1 through the PSA of network 2.
  • the association relationship may be an association relationship between S-NSSAI#1, S-NSSAI#2 and the identifier of network 2.
  • S-NSSAI#1 may be the S-NSSAI of service 1 in network 1.
  • Service 1 may also have other S-NSSAI in network 1, which is not limited. Since service 1 is deployed in network 2 but not in network 1, S-NSSAI#1 can be understood as the mapping of S-NSSAI#2 in network 1.
  • S-NSSAI#1 is different from the S-NSSAI of any ordinary service. Because if there is a certain S-NSSAI, which is both the S-NSSAI of a common service and the mapping of the S-NSSAI of service 1 in network 1, then AMF cannot distinguish the two services based on S-NSSAI#1. There is no way to determine whether to choose SMF2 based on this.
  • S-NSSAI#1 is an identifier defined to facilitate the selection of SMF2.
  • the slice corresponding to S-NSSAI#1 can also be understood as a slice that exists virtually in Network 1.
  • the common services mentioned in the embodiments of this application may refer to services that are not only allowed to be accessed by PSA through the network where the service is deployed, but also are allowed to be accessed by PSA through all other networks except this network.
  • the network includes network 1, network 2 and network 3.
  • Service a is deployed on network 1.
  • Service a is allowed to be accessed through the PSA of network 1, and is also allowed to be accessed through the respective PSA of network 2 and network 3.
  • service a can be considered as an ordinary business. If a service not only allows PSA access through the network where the service is deployed, but also allows PSA access through other parts of the network other than this network, the service can be understood as an ordinary service or a service of the nature X, regardless of Make limitations.
  • the network includes network 1, network 2, and network 3.
  • Service a is deployed on network 1.
  • Service a allows PSA access through network 1 and allows PSA access through network 2, but does not allow PSA access through network 3.
  • the service a is a normal service
  • the service a is a service of X nature.
  • S-NSSAI#2 can be the S-NSSAI of service 1 in network 2. There is a slice corresponding to S-NSSAI#2 in network 2, such as slice 1, to provide the services required by business 1. In addition, service 1 may also have other S-NSSAI in network 2, which is not limited.
  • the identity of network 2 may be PLMN2ID.
  • PLMN2ID in addition to network 1 and network 2, there may be other networks.
  • network 1 has also signed a contract with network 3.
  • S-NSSAI#2 may be the same as an S-NSSAI in network 3. Therefore, in order to avoid S-NSSAI#2 is associated with other networks. You can add the identifier of network 2 to the association relationship to ensure that S-NSSAI#2 can only be associated with network 2.
  • an implementation method of the association relationship can be as shown in Table 1 below.
  • S-NSSAI#1 is the S-NSSAI of service 1 in network 1.
  • S-NSSAI#2 is the S-NSSAI of service 1 in network 2.
  • S-NSSAI#3 is an S-NSSAI deployed in network 2, and other services with X properties (such as service 2) are deployed in network 1.
  • S-NSSAI#4 is the S-NSSAI of service 2 in network 2.
  • PLMN2ID is the identification of network 2.
  • S-NSSAI#a is an S-NSSAI deployed in other networks (such as network 3), and other services with X properties (such as service 3) are in network 1.
  • S-NSSAI #b service 3 is the S-NSSAI of network 3.
  • S-NSSAI#c is an S-NSSAI deployed in network 3, and other services with X properties (such as service 4) are deployed in network 1.
  • S-NSSAI#d is the S-NSSAI of service 4 in network 3.
  • PLMN3ID is the identification of network 3.
  • S-NSSAI#1-S-NSSAI#2 can be used to represent the same slice.
  • slice 1 is in the S-NSSAI of network 1 and network 2 respectively. This slice 1 exists in network 2 to provide the services required by service 1.
  • S-NSSAI#3-S-NSSAI#4 can be used to represent the same slice.
  • slice 2 is the S-NSSAI of network 1 and network 2 respectively. This slice 2 exists in network 2 and can be used to provide the services required by service 2.
  • S-NSSAI#aS-NSSAI#b can be used to represent the same slice.
  • slice 3 is the S-NSSAI of network 1 and network 3 respectively. This slice 3 exists in network 3 to provide the services required by business 3.
  • S-NSSAI#cS-NSSAI#d can be Used to represent the same slice.
  • slice 4 is in the S-NSSAI of network 1 and network 3 respectively. This slice 4 exists in network 3 to provide the services required by business 4.
  • any two or more services among services 1 to 4 may be the same service. That is, the same business may need multiple slices to provide the services it requires.
  • Table 2 can be used to characterize the mapping relationship of slices, such as the mapping relationship between S-NSSAI.
  • Table 3 can be used to characterize the deployment relationship of slices, such as the corresponding relationship between S-NSSAI and PLMN ID, which is also used to indicate which network the slices in Table 2 belong to. That is, in this case, the association relationship can be composed of two relationships, namely the mapping relationship of slices and the deployment relationship of slices.
  • Table 2 is similar to the "mapping of S-NSSAI" in the existing standard, but the difference is that the "mapping of S-NSSAI” in the existing standard only includes the mapping relationship between HPLMN and a slice of VPLMN.
  • the mapping relationship of slices in Table 2 can be a mapping relationship between slices of multiple different networks, and is not limited to HPLMN and VPLMN.
  • Table 3 is different from any entry in the existing standards, because in the roaming scenario, since the UE has accessed/registered to the VPLMN, the VPLMN is determined, or unique, so there is no need for it in the existing standards.
  • the mapping relationship of the slice indicates which HPLMN and VPLMN this set of mapping relationships belong to, so there is no need for the deployment information of the above slices. In other words, Table 3 may be a newly defined entry.
  • association relationship also needs to meet the following restrictions: if there are services of different nature Each is different, and the S-NSSAI of any service in network 1 needs to be different from the S-NSSAI of other services in network 2. This is because if the same S-NSSAI exists, then after the AMF receives the S-NSSAI from the UE, it cannot determine which service's S-NSSAI the S-NSSAI is, nor can it determine which S-NSSAI the S-NSSAI corresponds to. The S-NSSAI association of the service causes the process to fail.
  • Network 1 when determining the slice mapping, Network 1 will usually negotiate with other networks, such as Network 2 (this negotiation may be commercial, such as SLA, etc., and is not necessarily implemented through 3GPP or other network steps) to ensure that each S- NSSAI is the only one.
  • this negotiation may be commercial, such as SLA, etc., and is not necessarily implemented through 3GPP or other network steps
  • S-NSSAI#1, S-NSSAI#3, S-NSSAI#a and S-NSSAI#c are different
  • S-NSSAI#2, S-NSSAI#4 , S-NSSAI#b and S-NSSAI#d are different
  • association relationships are only some exemplary implementations of association relationships and are not limiting.
  • the association relationship may not include the identifier of Network 2, that is, the association relationship may only be S-NSSAI.
  • AMF can The association relationship is configured locally, for example, the association relationship is stipulated or configured through the roaming agreement between operators, or the association relationship can be obtained from other network elements (such as NSSF, etc.).
  • the association relationship may be PLMN granular information and may not be related to the UE or PDU session. Therefore, the AMF's acquisition of the association relationship can be considered as an enhancement of the AMF's ability to perceive its own information.
  • AMF obtains S-NSSAI list 1.
  • S-NSSAI list 1 may include S-NSSAI (including S-NSSAI#1) of services with X properties (including service 1) in network 1.
  • S-NSSAI list 1 can be used by the AMF to determine whether the received S-NSSAI is the S-NSSAI of the X-nature service or the S-NSSAI of the ordinary service.
  • AMF can obtain S-NSSAI list 1 from PCF through the registration process.
  • S-NSSAI list 1 is carried in the AMF policy control creation (Npcf_AMFPolicyControl_Create) message in the registration process, or in any possible message in the registration process, without limitation.
  • AMF's acquisition of S-NSSAI list 1 can be considered as an enhancement to the existing registration process.
  • AMF can also obtain S-NSSAI list 1 from other possible network elements, such as NSSF.
  • the AMF policy control creation message can be replaced with a network slice (NSS) selection acquisition (Nnssf_NSSelection_Get) message, or an NSSAI availability update (Nnssf_NSSAIAvailability_Update) message or other possible messages.
  • NSS network slice
  • Nnssf_NSSelection_Get network slice
  • NSSAIAvailability_Update NSSAI availability update
  • AMF can also obtain S-NSSAI list 1 through other methods, such as local configuration.
  • the AMF executes the processing logic of ordinary services by default, that is, selects a corresponding SMF based on the S-NSSAI.
  • this S-NSSAI is the S-NSSAI of a service of the nature Business of X nature. Therefore, the AMF can obtain the S-NSSAI list 1 to determine whether the received S-NSSAI is the S-NSSAI of the X-nature service or the S-NSSAI of the ordinary service. If it is the S-NSSAI of a normal service, the AMF executes the processing logic of the normal service. If it is the S-NSSAI of a service of X nature, the AMF can match it with the relationship association to determine the SMF in network 1 and the SMF in network 2. For details, please refer to S505 below, which will not be described again.
  • any S-NSSAI in S-NSSAI List 1 is different from the H-S-NSSAI of any common service deployed in Network 1.
  • This can be understood as the premise assumption for the solution of this embodiment to be established, because if there is a certain S-NSSAI, it is not only the S-NSSAI of a certain ordinary service deployed in the network 1, but also the service of a certain nature X in the network 1 S-NSSAI, the AMF cannot distinguish the two services based on the S-NSSAI, and cannot determine whether to select SMF in network 2 based on this.
  • S501 is an optional step.
  • AMF does not need to obtain S-NSSAI list 1.
  • AMF can match the received S-NSSAI with the association relationship by default to determine the S-NSSAI. Is it S-NSSAI for X-type services or S-NSSAI for ordinary services?
  • AMF sends a registration accept message to the UE.
  • the UE receives the registration accept message from the AMF.
  • the AMF may send a registration acceptance message to the UE during the registration process to indicate that the UE is allowed to register with the network 1.
  • the registration acceptance message can include S-NSSAI#1 and Allowed NSSAI#1.
  • S-NSSAI#1 can be carried in existing cells to reduce implementation difficulty, such as in the UE route selection policy (URSP), used to indicate that the S-NSSAI of service 1 is S-NSSAI#1, or It can also be carried in newly defined cells to improve implementation flexibility without limitation.
  • Allowed NSSAI#1 may include S-NSSAI#1 to indicate that the slice corresponding to S-NSSAI#1 is a slice available to the UE, or a slice that is authorized to be accessed or used by the UE. Allowed NSSAI#1 may also include other S-NSSAI besides S-NSSAI#1, such as the S-NSSAI of services deployed in network 1.
  • the information that AMF has sensed includes: association relationship and S-NSSAI list 1.
  • the information that the UE has sensed includes: S-NSSAI#1, and Allowed NSSAI#1. Both parties can establish a session accordingly.
  • the UE may not be aware of the S-NSSAI of which network the S-NSSAI#1 it obtained is. That is, in scenario 1, the UE can process S-NSSAI#1 according to existing standard processing methods, such as using or sending. In other words, the UE may think that the above-mentioned S-NSSAI#1 is actually a common S-NSSAI, such as the S-NSSAI of the service deployed by network 1, and the UE may not be aware of whether it needs to access the service through V-PSA.
  • S501 and S502 are executed during the registration process, but there is no triggering relationship.
  • the registration process in the embodiment of this application has also evolved into a corresponding process.
  • the registration process can be replaced with any possible process, and the registration acceptance message can be correspondingly replaced with any possible message without limitation.
  • S503 The UE determines to trigger session establishment.
  • the UE When wanting to access service 1, the UE can obtain S-NSSAI#1, for example, determine the S-NSSAI of service 1 as S-NSSAI#1 according to the URSP. The UE can use S-NSSAI#1 and Allowed NSSAI#1 for authentication, if it is determined that Allowed NSSAI#1 contains S-NSSAI#1. In this way, the UE determines that the authentication is passed, thereby determining to trigger the establishment of a PDU session, and executes S504. Of course, if authentication fails, execution can continue as is.
  • the UE sends a PDU session establishment request (PDU session establishment request) message to the AMF.
  • the AMF receives the PDU session establishment request message from the UE.
  • the PDU session establishment request message may be used to request the establishment of a PDU session.
  • it includes S-NSSAI#1, which is used to request the establishment of a PDU session for the S-NSSAI#1, that is, the PDU session of service 1.
  • AMF determines SMF2 based on S-NSSAI#1.
  • the AMF may determine the identifier associated with S-NSSAI#2 and network 2 based on S-NSSAI#1 from the UE, that is, S-NSSAI#1 in the PDU session establishment request message. For example, AMF can traverse S-NSSAI list 1 based on S-NSSAI#1 to determine that S-NSSAI list 1 contains S-NSSAI#1, and thereby determine the S-NSSAI# based on S-NSSAI#1 and the association relationship. 1 Identity associated with S-NSSAI#2 and Network 2.
  • the AMF can directly determine the identity of the S-NSSAI#1 associated with S-NSSAI#2 and network 2 based on the S-NSSAI#1 and the association relationship. Among them, if the association relationship is implemented in the manner of Table 1, the AMF can use S-NSSAI#1 to query Table 1 to determine the identifier of the S-NSSAI#1 associated with S-NSSAI#2 and network 2.
  • AMF can first use S-NSSAI#1 to query Table 2 to determine that S-NSSAI#1 is associated with S-NSSAI#2, and then use S-NSSAI#2 to query Table 3, to determine that S-NSSAI#2 is associated with PLMN2ID, that is, determine that S-NSSAI#1 is associated with PLMN2ID.
  • this sub-table query method can also be summarized as AMF determines that S-NSSAI#1 is associated with S-NSSAI#2 and network 2 based on the mapping relationship between S-NSSAI#1, the slice and the deployment relationship of the slice. logo.
  • AMF can select SMF1 based on S-NSSAI#1. Its specific implementation is similar to the existing standards and can be understood by reference without going into details. However, what is different from the AMF selecting SMF in the existing standard is that since the PSA corresponding to the DNN in the embodiment of the present application is located in network 2, it is not managed/controlled by SMF1 in network 1. Therefore, when the AMF selects SMF1 in network 1, it can DNN is not considered. And, the AMF can select SMF2 based on the identification of S-NSSAI#2 and network 2.
  • the AMF can send the identifier of S-NSSAI#2 and network 2 to the NRF, such as sending an NF discovery request (Nnrf_NFDiscovery_Request) message carrying the identifier of S-NSSAI#2 and network 2, and the NF discovery request message indicates that the discovered The network element is SMF.
  • NRF can select SMF2 according to the NF discovery request message, thereby returning the address or identification of SMF2 to the AMF.
  • the AMF returns an NF discovery response (Nnrf_NFDiscovery_Response) message carrying the address or identification of SMF2.
  • the AMF determines that the S-NSSAI from the UE is not in S-NSSAI List 1, or there is no matching S-NSSAI and network identification in the association relationship, the AMF executes the existing process.
  • AMF may also select SMF2 based only on S-NSSAI#2.
  • AMF can associate S-NSSAI#1 with SMF2 by default, so that AMF determines SMF2 directly based on S-NSSAI#1.
  • AMF can associate S-NSSAI#2 with SMF1 by default, so that AMF directly determines SMF1 based on S-NSSAI#2.
  • S506 AMF sends the identifier of SMF2 to SMF1.
  • SMF1 receives the identification of SMF2 from the AMF.
  • the SMF2 identifier can be carried in the PDU session creation context (Nsmf_PDUSession_CreateSMContext) message, or it can be carried in any other possible message, without limitation.
  • AMF obtains the address of SMF2 in S505
  • AMF can convert the address of SMF2 into the identifier of SMF2, and then encapsulate the identifier of SMF2 into the PDU session creation context message; or, AMF can also directly send SMF2 to SMF1
  • the address is not limited.
  • SMF1 selects UPF and configures the N4 session corresponding to UPF.
  • SMF1 can create a context based on the PDU session, select the UPF in network 1, and configure the N4 session for the UPF.
  • SMF1 sends a PDU session creation request (Nsmf_PDUSession_Create Request) message to SMF2.
  • SMF2 receives the PDU session creation request message from SMF1.
  • the PDU session creation request message may include at least one of the following: indication information, an identifier of the first service, or UE location information.
  • the instruction information can be used to instruct SMF2 to select PSA and not select the non-anchor UPF, that is, the offload point in Network 2.
  • the identifier of the first service is used to select a PSA that supports access to the first service.
  • the UE location information may include at least one of the following: tracking area (TA) information (such as tracking area code (TAC) or tracking area identity (TAI)), cell identification (cell ID) , data network access identifier (DNAI), or actual location information, such as latitude and longitude information or geographical location information (such as XX city, XX county, XX district, etc.).
  • tracking area such as tracking area code (TAC) or tracking area identity (TAI)
  • cell ID cell ID
  • DNAI data network access identifier
  • actual location information such as latitude and longitude information or geographical location information (such as XX city, XX county, XX district, etc.).
  • SMF1 configures the corresponding relationship between the location information that can be identified by network 1 and the UE location information that can be identified by network 2. For example, SMF1 configures the corresponding relationship between the TAI of network 1 and the DNAI of network 2. In this case, SMF1 can determine the location information that network 1 can identify based on the current location of the UE, such as the TAI of network 1, and thereby determine the location information of network 1 corresponding to the current location of the UE and the corresponding relationship.
  • the identified UE location information such as the DNAI of network 2 then sends the UE location information that network 2 can identify to SMF2, so that SMF2 can select a PSA accordingly.
  • SMF1 may be locally preconfigured by SMF1
  • SMF1 may be obtained by SMF1 from AF, or may be sensed by SMF1 through other methods, without limitation.
  • SMF2 configures the corresponding relationship between the UE location information that can be identified by network 1 and the location information that can be identified by network 2.
  • SMF1 can send UE location information that can be identified by Network 1 to SMF2 based on the current location of the UE.
  • SMF2 After receiving the UE location information that can be identified by Network 1, SMF2 can determine the location information that Network 2 can identify corresponding to the UE's current location based on the UE location information that Network 1 can identify and the corresponding relationship, and select a PSA accordingly.
  • the corresponding relationship may be locally preconfigured by SMF2, may be obtained by SMF2 from other network elements, or may be sensed by SMF1 through other methods, without limitation.
  • SMF1 can send the actual location information of the UE to SMF2.
  • SMF1 can determine the location information that Network 1 can recognize based on the current location of the UE, such as TA information, TAI, etc., convert the location information that Network 1 can recognize into longitude and latitude information, and then send the longitude and latitude information to SMF2.
  • SMF2 can convert the latitude and longitude information into location information that can be recognized by Network 2, such as cell identification, DNAI, etc., to select a PSA accordingly.
  • SMF1 can locally convert between location information and longitude and latitude information, or it can also be implemented with the help of other network elements, such as location management function (LMF), without limitation.
  • LMF location management function
  • SMF2 can also locally convert between UE location information and latitude and longitude information, or it can also be implemented with the help of other network elements, without limitation.
  • SMF2 selects PSA, configures the N4 session corresponding to PSA, and selects EASDF, and configures the DNS processing rules corresponding to EASDF.
  • SMF2 may determine that it is necessary to select the PSA in network 2 instead of the offloading point in network 2 based on the indication information. In this way, SMF2 can select an appropriate PSA based on the identity of the first service and the UE location information, such as a PSA that is relatively close to the UE, has a relatively low load, and supports the first service.
  • SMF2 sends a PDU session creation response (Nsmf_PDUSession_Create Response) message to SMF1.
  • SMF1 receives the PDU session creation response message from SMF2.
  • the PDU session creation response message can be used to indicate that SMF2 has selected PSA and EASDF, such as including the address of PSA and the address of EASDF.
  • S511, SMF1 and SMF2 establish user plane connections.
  • SMF1 can provide the address of the PSA, the address of the RAN accessed by the UE, the address of the EASDF (optional), and the address of the UE (optional) to the UPF, and provide the address of the UPF to the RAN. SMF1 can also provide the UPF address to SMF2 so that SMF2 provides the UPF address to the PSA. At this point, both PSA and UPF have obtained each other's addresses, and the user plane connection between network 1 and network 2 is successfully established, that is, the PDU session of service 1 is successfully established.
  • SMF1 sends a PDU session establishment accept message to the UE.
  • the UE receives the PDU session establishment accept message from SMF1.
  • the address of EASDF can be carried in the PDU session establishment accept message.
  • the UE can send a request message carrying the address of the EASDF through the user plane connection.
  • UPF1 obtains the address of the EASDF, it can determine that the UE needs to access the PSA, and thus sends the request message to the PSA, so that the PSA responds to the request message and provides the UE with services corresponding to business 1.
  • AMF can determine SMF1 based on S-NSSAI#1 of service 1 in network 1, and S-NSSAI#2 of service 1 in network 2, and determine SMF2 based on S-NSSAI#2.
  • SMF1 and SMF2 can establish a user plane connection, so that The UE can access service 1 through the PSA of network 2.
  • FIG. 6 is a schematic flowchart 2 of the communication method provided by the embodiment of the present application.
  • the S-NSSAI associated with service 1 may be S-NSSAI#2 of service 1 in network 2.
  • AMF can determine SMF2 based on S-NSSAI#2, and S-NSSAI#1 of service 1 in network 2, and determine SMF1 based on S-NSSAI#1.
  • SMF1 and SMF2 can establish a user plane connection, so that the UE can access service 1 through the PSA of network 2.
  • AMF obtains S-NSSAI list #2 from PCF.
  • S-NSSAI list #2 may include S-NSSAI (including S-NSSAI#2) of services with X properties (including service 1) in network 2. Similar to the above S-NSSAI List 1, S-NSSAI List #2 can also be used by the AMF to determine whether the received S-NSSAI is an S-NSSAI for X-nature services or an S-NSSAI for ordinary services. Among them, the common service may be a service deployed on network 1 and accessible through the PSA of network 1. In addition, the specific method for AMF to obtain S-NSSAI list #2 can refer to the relevant introduction in S501 above, and will not be described again.
  • S601 is an optional step.
  • AMF does not need to obtain S-NSSAI list #2.
  • AMF can match the received S-NSSAI with the association relationship by default to determine the S-NSSAI. Is it S-NSSAI for X-type services or S-NSSAI for ordinary services?
  • the AMF sends a registration acceptance message to the UE.
  • the UE receives the registration accept message from the AMF.
  • the AMF may send a registration acceptance message to the UE during the registration process to indicate that the UE is allowed to register with the network 1.
  • the registration acceptance message can include S-NSSAI#2 and Allowed NSSAI#2.
  • S-NSSAI#2 can be carried in existing cells to reduce implementation difficulty. For example, in URSP, the S-NSSAI used to indicate service 1 is S-NSSAI#2, or it can also be carried in newly defined cells. To improve implementation flexibility, there are no restrictions. Allowed NSSAI#2 may include S-NSSAI#2 to indicate that the slice corresponding to S-NSSAI#2 is a slice available to the UE, or an authorized slice.
  • Allowed NSSAI#2 may also include other S-NSSAI besides S-NSSAI#2, such as the S-NSSAI of services deployed in network 1. That is to say, the difference between S502 and S602 is that S502 provides Allowed NSSAI including S-NSSAI#1, and S602 provides Allowed NSSAI including S-NSSAI#2.
  • the information that AMF has sensed includes: association relationship and S-NSSAI list #2.
  • the information that the UE has sensed includes: S-NSSAI#2, and Allowed NSSAI#2 including S-NSSAI#2. Both parties can establish a session accordingly.
  • the UE may not be aware of the S-NSSAI of which network the S-NSSAI#2 it obtained is. That is, similar to scenario 1, the UE can also process S-NSSAI#2 according to the existing standard processing method. In other words, the UE may also think that the above-mentioned S-NSSAI#2 is actually the S-NSSAI of the ordinary service, and the UE may not be aware of whether it needs to access the service through V-PSA.
  • S601-S602 are executed during the registration process, but there is no triggering relationship.
  • the registration process in the embodiment of this application has also evolved into a corresponding process.
  • the registration process can be replaced by any possible process without limitation.
  • S603 The UE determines to trigger session establishment.
  • the UE When wanting to access service 1, the UE can obtain S-NSSAI#2, for example, determine the S-NSSAI of service 1 as S-NSSAI#2 according to the URSP. The UE can use S-NSSAI#2 and Allowed NSSAI#2 for authentication, if it is determined that Allowed NSSAI#2 contains S-NSSAI#2. In this way, the UE determines that the authentication is passed, thereby determining to trigger the establishment of a PDU session, and executes S604. Of course, if authentication fails, execution continues as is.
  • S604 The UE sends a PDU session establishment request message to the AMF.
  • the AMF receives the PDU session establishment request message from the UE.
  • S604 The difference between S604 and S504 is that the PDU session establishment request message of S604 carries S-NSSAI#2.
  • S-NSSAI#2 For the rest, please refer to the relevant introduction of S504, which will not be described again.
  • AMF determines SMF1 based on S-NSSAI#2.
  • the AMF may determine the identity associated with the S-NSSAI#2 to S-NSSAI#1 and network 2 based on the S-NSSAI#2 from the UE. For example, the AMF may traverse S-NSSAI list #2 based on S-NSSAI#2 to determine that S-NSSAI list #2 contains S-NSSAI#2. In this way, AMF can determine the identity of S-NSSAI#2 associated with S-NSSAI#1 and network 2 based on S-NSSAI#2 and the association relationship.
  • the AMF can directly determine the identity of the S-NSSAI#2 associated with S-NSSAI#1 and network 2 based on the S-NSSAI#2 and the association relationship. It can be understood that S605 is different from S505 in that S605 is used by AMF to query the association relationship using S-NSSAI#2, but its specific query logic is similar to the above-mentioned S505, which can be understood by reference and will not be described again.
  • AMF can select SMF1 based on S-NSSAI#1, and AMF can also select SMF2 based on S-NSSAI#2 and the identification of network 2.
  • SMF1 based on S-NSSAI#1
  • SMF2 select SMF2 based on S-NSSAI#2 and the identification of network 2.
  • S606 AMF sends the identifier of SMF2 to SMF1.
  • SMF1 receives the identification of SMF2 from the AMF.
  • SMF1 selects UPF and configures the N4 session corresponding to UPF.
  • S608 SMF1 sends a PDU session creation request message to SMF2.
  • SMF2 receives the PDU session creation request message from SMF1.
  • SMF2 selects PSA, configures the N4 session corresponding to PSA, and selects EASDF, and configures the DNS processing rules corresponding to EASDF.
  • S610 SMF2 sends a PDU session creation response message to SMF1.
  • SMF1 receives the PDU session creation response message from SMF2.
  • S611, SMF1 and SMF2 establish user plane connection.
  • S612 SMF1 sends a PDU session establishment acceptance message to the UE.
  • the UE receives the PDU session establishment accept message from SMF1.
  • S606-S612 can refer to the relevant introduction of S506-S512, and will not be described again.
  • AMF can determine SMF2 based on S-NSSAI#2 of service 1 in network 1, and determine SMF1 based on S-NSSAI#1 of service 1 in network 1. In this way, SMF1 and SMF2 can establish a user plane connection, so that the UE can access service 1 through the PSA of network 2.
  • FIG. 7 is a schematic flowchart 3 of the communication method provided by the embodiment of the present application.
  • the S-NSSAI associated with service 1 may include S-NSSAI#1 of service 1 in network 1, and S-NSSAI#2 of service 1 in network 2.
  • the AMF may provide S-NSSAI#2 and the association relationship between S-NSSAI#1 and S-NSSAI#2 to the UE in advance.
  • the UE wants to access service 1
  • the UE can send S-NSSAI#1 and S-NSSAI#2 to the AMF, so that the AMF determines SMF1 based on S-NSSAI#1 and determines SMF1 based on S-NSSAI#. 2, and the identification of network 2 (optional), determine SMF2.
  • SMF1 and SMF2 can establish a user plane connection, so that the UE can access service 1 through the PSA of network 2.
  • the restriction conditions of the association relationship may also be similar to S500.
  • each S-NSSAI in the association can be unique.
  • the restriction conditions of the association relationship may be different from those of S500.
  • the S-NSSAI of each service is different in network 1 and a network other than network 1.
  • S-NSSAI#1, S-NSSAI#2, S-NSSAI#3 and S-NSSAI#4 are different, and S-NSSAI#a, S-NSSAI#b, S -NSSAI#c and S-NSSAI#d are different.
  • the S-NSSAI of each service in network 1 and a network other than network 1 is the same as the S-NSSAI of each service in network 1 and a network other than network 1.
  • the S-NSSAI of another network other than Network 1 may be the same, that is, each S-NSSAI in the association may not be unique. In this case, it may be necessary to distinguish these same S-NSSAI through network identification.
  • the S-NSSAI in S-NSSAI#1, S-NSSAI#2, S-NSSAI#3 and S-NSSAI#4 may be the same as S-NSSAI#a and S-NSSAI#.
  • the S-NSSAI in S-NSSAI#c and S-NSSAI#d are the same. Therefore, it is necessary to pass These same S-NSSAIs are distinguished by PLMN2ID and PLMN3ID.
  • the AMF sends a registration acceptance message to the UE.
  • the UE receives the registration accept message from the AMF.
  • the AMF may send a registration acceptance message to the UE during the registration process to indicate that the UE is allowed to register with the network 1.
  • the registration acceptance message can include S-NSSAI#1, association, and Allowed NSSAI#1.
  • S-NSSAI#1 and Allowed NSSAI#1 can refer to the relevant introduction in S501 above, and will not be described again.
  • the association relationship can also be carried in the same cell as the above-mentioned S-NSSAI#1, such as USRP; or the association relationship can also be carried independently in other existing cells to reduce the difficulty of implementation, or in newly defined cells to Improve implementation flexibility without limitations.
  • the registration acceptance message may also include the identity of Network 2.
  • the identity of Network 2 may be carried in the USRP together with S-NSSAI#1 to indicate that Service 1 is deployed in Network 2, or the identity of Network 2 may also be carried in the USRP. It can be carried independently in existing cells to reduce implementation difficulty, or in newly defined cells to improve implementation flexibility, without limitation.
  • the information AMF has sensed includes: association relationships.
  • the information that the UE has sensed includes: S-NSSAI#1, the identity of Network 2 (optional), the association relationship, and Allowed NSSAI#1 containing S-NSSAI#1. Both parties can establish a session accordingly.
  • the AMF may provide the UE with the identity of Network 2, or may not provide the identity of Network 2 without limitation.
  • the AMF needs to provide the UE with the identity of network 2 so that the UE can determine the unique S-NSSAI.
  • performing S701 in the registration process are just some examples. With the evolution of standards, the registration process in the embodiment of this application has also evolved into a corresponding process. Alternatively, the registration process can be replaced by any possible process without limitation.
  • S702 The UE determines to trigger session establishment.
  • the UE can obtain S-NSSAI#1 and the identity of network 2 (optional). For example, the UE may determine, according to the URSP, that the S-NSSAI of service 1 is S-NSSAI#1, and the identifier of the network where service 1 is deployed is the identifier of network 2 (optional). UE can use S-NSSAI#1 and Allowed NSSAI for authentication. For example, the UE can determine whether Allowed NSSAI#1 contains S-NSSAI#1 based on S-NSSAI#1. If Allowed NSSAI#1 contains S-NSSAI#1, the authentication passes. Otherwise, the authentication fails and the execution continues in the existing manner.
  • the UE can determine S-NSSAI#2 based on S-NSSAI#1 and the association, and trigger the establishment accordingly. PDU session.
  • the UE can determine S-NSSAI#2 based on the identification and association of S-NSSAI#1, Network 2, and trigger the establishment of a PDU session accordingly.
  • the specific implementation of the UE determining S-NSSAI#2 is similar to the above-mentioned S505, which can be understood by reference and will not be described again.
  • the UE can determine S-NSSAI#2 and the network based on S-NSSAI#1 and the association relationship. 2, or the UE can determine S-NSSAI#2 based on S-NSSAI#1 and the association relationship, but is not sure of the identity of network 2, and the S-NSSAI#2 at this time is unique.
  • the execution logic of the UE in S702 is only an example and is not limited.
  • the UE can also first use S-NSSAI#1 and the identifier of Network 2 (optional) to query the association relationship to determine the S-NSSAI#1 and the identifier of Network 2 (optional). NSSAI#2, and then use S-NSSAI#1 and Allowed NSSAI for authentication.
  • the UE sends a PDU session establishment request message to the AMF.
  • the AMF receives the PDU session establishment request message from the UE.
  • the UE since the UE obtained S-NSSAI#1, S-NSSAI#2, and the identity of network 2 (optional) in S702, the UE can carry S-NSSAI#1, S-NSSAI in the PDU session establishment request message. #2, and the identifier of network 2 (optional), are used to request the establishment of a PDU session for the S-NSSAI#1 and S-NSSAI#2, that is, the PDU session of service 1.
  • the UE may not carry the identity of Network 2 in S703.
  • AMF determines SMF1 based on S-NSSAI#1 and determines SMF2 based on S-NSSAI#2.
  • AMF sends the identifier of SMF2 to SMF1.
  • SMF1 receives the identification of SMF2 from the AMF.
  • SMF1 selects UPF and configures the N4 session corresponding to UPF.
  • SMF1 sends a PDU session creation request message to SMF2.
  • SMF2 receives the PDU session creation request message from SMF1.
  • SMF2 selects PSA, configures the N4 session corresponding to PSA, and selects EASDF, and configures the DNS processing rules corresponding to EASDF.
  • SMF2 sends a PDU session creation response message to SMF1.
  • SMF1 receives the PDU session creation response message from SMF2.
  • S710, SMF1 and SMF2 establish user plane connections.
  • SMF1 sends a PDU session establishment acceptance message to the UE.
  • the UE receives the PDU session establishment accept message from SMF1.
  • S705-S711 can refer to the relevant introduction of S506-S512, and will not be described again.
  • the AMF can determine SMF1 based on S-NSSAI#1 and determine SMF1 based on S-NSSAI#1. NSSAI#2, confirm SMF2. In this way, SMF1 and SMF2 can establish a user plane connection, so that the UE can access service 1 through the PSA of network 2.
  • FIG. 8 is a schematic flowchart 4 of the communication method provided by the embodiment of the present application.
  • the AMF can provide S-NSSAI#2 and the association relationship between S-NSSAI#1 and S-NSSAI#2 to the UE in advance.
  • the UE can send S-NSSAI#1 and S-NSSAI#2 to the AMF, so that the AMF determines SMF1 based on S-NSSAI#1 and determines SMF1 based on S-NSSAI#. 2, and the identification of network 2 (optional), determine SMF2.
  • SMF1 and SMF2 can establish a user plane connection, so that the UE can access service 1 through the PSA of network 2.
  • S800 can refer to the relevant introduction in the above S700, and will not be described again.
  • the AMF sends a registration acceptance message to the UE.
  • the UE receives the registration accept message from the AMF.
  • the AMF may send a registration acceptance message to the UE during the registration process to indicate that the UE is allowed to register with the network 1.
  • the registration acceptance message can include S-NSSAI#2, association, and Allowed NSSAI#2.
  • S-NSSAI#2 can refer to the relevant introduction in S601 above, and will not be described again.
  • the association relationship can also be carried in the same cell as the above-mentioned S-NSSAI#2, such as USRP; or the association relationship can be carried independently in existing cells to reduce implementation difficulty, or in newly defined cells to improve Achieve flexibility without limitations.
  • Allowed NSSAI#2 you can still refer to the relevant introduction in S601 above and will not go into details.
  • Allowed NSSAI#2 can also be replaced with a corresponding relationship, such as the corresponding relationship between the identifier of network 2 and S-NSSAI#2, to indicate that the available slices in network 2 include slices corresponding to S-NSSAI#2.
  • the corresponding relationship may also include the corresponding relationship between the identifier of network 2 and other S-NSSAI
  • the corresponding relationship may also include the corresponding relationship between the identifier of other networks and other S-NSSAI.
  • Table 4 can be used to characterize: the available slices in network 1 (PLMN1ID) are slices corresponding to S-NSSAI#1, S-NSSAI#3, S-NSSAI#a and S-NSSAI#c, and network 2 (PLMN2ID)
  • the available slices in are the slices corresponding to S-NSSAI#2 and S-NSSAI#4, and the available slices in network 3 (PLMN3ID) are the slices corresponding to S-NSSAI#b and S-NSSAI#d.
  • the registration acceptance message may also include the identity of Network 2.
  • the identity of Network 2 may be carried in the USRP together with S-NSSAI#1 to indicate that Service 1 is deployed in Network 2, or the identity of Network 2 may also be carried in the USRP. It can be carried independently in existing cells to reduce implementation difficulty, or in newly defined cells to improve implementation flexibility, without limitation.
  • S801 can also refer to the relevant introduction in S701 above, and will not be described again.
  • S802 The UE determines to trigger session establishment.
  • the UE can obtain S-NSSAI#2 and the identity of network 2 (optional). For example, the UE may determine, according to the URSP, that the S-NSSAI of service 1 is S-NSSAI#2, and the identifier of the network where service 1 is deployed is the identifier of network 2 (optional). On this basis, the UE can use S-NSSAI#2 and Allowed NSSAI#2 for authentication. For example, the UE can determine whether Allowed NSSAI#2 contains S-NSSAI# based on S-NSSAI#2. If Allowed NSSAI#2 contains S-NSSAI#2, the authentication passes. Otherwise, the authentication fails and the execution continues in the existing manner.
  • the UE may also use S-NSSAI#2, the identity of Network 2 and the corresponding relationship for authentication. For example, the UE may determine, based on the identifier of Network 2, that the corresponding relationship has the identifier of the network corresponding to it, that is, the identifier of Network 2, thereby obtaining the S-NSSAI corresponding to the identifier of Network 2 in the corresponding relationship. The UE can verify whether S-NSSAI#2 is in the S-NSSAI corresponding to the identity of network 2. If the S-NSSAI corresponding to the identifier in network 2 is used, the authentication passes. Otherwise, the authentication fails and the execution continues in the existing manner.
  • each S-NSSAI in the association is unique, the UE can determine S-NSSAI#1 based on S-NSSAI#2 and the association, and trigger the establishment accordingly. PDU session.
  • the UE can determine S-NSSAI#1 based on the identification and association of S-NSSAI#2, network 2, and trigger the establishment of a PDU session accordingly.
  • the specific implementation of the UE determining S-NSSAI#1 is similar to the above-mentioned S505, which can be understood by reference and will not be described again.
  • the UE can determine S-NSSAI#1 and the network based on S-NSSAI#2 and the association relationship. 2, or the UE can determine S-NSSAI#1 based on S-NSSAI#2 and the association relationship, but is not sure of the identity of network 2, and S-NSSAI#2 at this time is unique.
  • S803 The UE sends a PDU session establishment request message to the AMF.
  • the AMF receives the PDU session establishment request message from the UE.
  • S803 can refer to the relevant introduction of S703, and will not be described again.
  • the UE may not carry the identity of network 2 in step S803.
  • AMF determines SMF1 based on S-NSSAI#1 and determines SMF2 based on S-NSSAI#2.
  • AMF sends the identifier of SMF2 to SMF1.
  • SMF1 receives the identification of SMF2 from the AMF.
  • SMF1 selects UPF and configures the N4 session corresponding to UPF.
  • S807 SMF1 sends a PDU session creation request message to SMF2.
  • SMF2 receives the PDU session creation request message from SMF1.
  • SMF2 selects PSA, configures the N4 session corresponding to PSA, and selects EASDF, and configures the DNS processing rules corresponding to EASDF.
  • SMF2 sends a PDU session creation response message to SMF1.
  • SMF1 receives the PDU session creation response message from SMF2.
  • S810, SMF1 and SMF2 establish user plane connections.
  • SMF1 sends a PDU session establishment acceptance message to the UE.
  • the UE receives the PDU session establishment accept message from SMF1.
  • S805-S811 can refer to the relevant introduction of S506-S512, and will not be described again.
  • the AMF can determine SMF1 based on S-NSSAI#1 and determine SMF1 based on S-NSSAI#1. NSSAI#2, confirm SMF2. In this way, SMF1 and SMF2 can establish a user plane connection, so that the UE can access service 1 through the PSA of network 2.
  • FIG. 9 is a schematic flow chart 5 of the communication method.
  • This communication method mainly involves the interaction between access and mobility management network elements and terminals.
  • the access and mobility management network element may specifically be the AMF in Scenario 1 to Scenario 4 above.
  • the terminal may specifically be the UE in the above scenarios 1 to 4.
  • the terminal sends a session establishment request message to the access and mobility management network element.
  • the access and mobility management network receives a session establishment request message from the terminal.
  • the access and mobility management network element can be deployed in the first network (such as the above-mentioned network 1).
  • the first network may be the terminal's home network, and the terminal may access the home network.
  • the second network (such as network 2 above) may be a network other than the home network.
  • the second network is deployed with a first service (such as the above-mentioned service 1), and the first service may be a service that needs to be accessed through a session anchor point of the second network.
  • the session establishment request message (such as the above-mentioned PDU session establishment request message) may include the slice identifier associated with the first service.
  • the slice identifier associated with the first service may be the first slice identifier of the first service in the home network (such as the above-mentioned S-NSSAI #1).
  • the access and mobility management network element may send the first slice identifier to the terminal, and accordingly, the terminal may receive the first slice identifier from the access and mobility management network element to Ensure that the terminal can subsequently feed back the first slice identifier, such as feeding back the first slice identifier through S901.
  • the first slice identifier sent by the access and mobility management network element to the terminal can be carried in the URSP of the terminal, That is, it can be carried in existing cells to reduce implementation difficulty, or it can also be carried in new cells to improve implementation flexibility, without limitation.
  • the access and mobility management network element can not only send the first slice identifier to the terminal, but also send the allowed first slice identifier list to the terminal (such as the above Allowed NSSAI#1 ), used to authenticate the first slice identifier.
  • the slice identifier associated with the first service may be the second slice identifier of the first service in the second network (such as the above-mentioned S-NSSAI#2).
  • the access and mobility management network element can send the second slice identifier to the terminal, and accordingly, the terminal can receive the second slice identifier from the access and mobility management network element to ensure that the terminal The second slice identifier can be fed back later.
  • the second slice identifier sent by the access and mobility management network element to the terminal can be carried in the URSP of the terminal, that is, It can be carried in existing cells to reduce the difficulty of implementation, or it can be carried in new cells to improve implementation flexibility, without limitation.
  • the access and mobility management network element can not only send the second slice identifier to the terminal, but also send the allowed second slice identifier list to the terminal (such as Allowed NSSAI#2 above). Used to authenticate the second slice identifier.
  • the slice identifier associated with the first service may include a first slice identifier and a second slice identifier.
  • the association relationship may be the association relationship between the first slice identifier, the second slice identifier and the identifier of the second network (such as the above-mentioned association relationship between S-NSSAI#1, S-NSSAI#2 and the identifier of network 2).
  • the terminal can query the association relationship based on the first slice identifier, the identifier of the second network (such as the identifier of the above-mentioned network 2) and the association relationship, such as using the first slice identifier and the identifier of the second network, to facilitate the determination.
  • the second slice identifier associated with the first slice identifier and the identifier of the second network enables the terminal to determine the second slice identifier, simplifying the implementation complexity of access and mobility management network elements and reducing network side overhead.
  • the terminal may locally pre-configure the first slice identifier, the identifier of the second network, and the association relationship.
  • the access and mobility management network element may send the association relationship, the first slice identity, and the second association relationship to the terminal. The identity of the network; accordingly, the terminal can receive the association relationship between the access and mobility management network elements, the first slice identity, and the identity of the second network.
  • the first slice identifier and the identifier of the second network are sent by the access and mobility management network element to the terminal, or the first slice identifier and the second network identifier are received by the terminal from the access and mobility management network element.
  • the identifier can be carried in the URSP of the terminal, that is, carried in existing cells to reduce the difficulty of implementation, or it can also be carried in new cells to improve implementation flexibility, without limitation.
  • the access and mobility management network element can obtain the association relationship in advance from the policy control network element (such as the above-mentioned PCF) or the network slice selection network element (such as the above-mentioned NSSF), or can also obtain the association from any other possible network element. relationship, or local preconfigured association relationship.
  • PCF policy control network element
  • the network slice selection network element such as the above-mentioned NSSF
  • the association relationship may be the association relationship between the first slice identifier and the second slice identifier (such as the above-mentioned association relationship between S-NSSAI#1 and S-NSSAI#2).
  • the terminal can use the first slice identifier and association relationship, such as using the first
  • the slice identifier queries the association relationship to facilitate the determination of the second slice identifier associated with the first slice identifier, that is, the terminal determines the second slice identifier to simplify the implementation complexity of access and mobility management network elements and reduce the network side overhead.
  • the terminal may locally pre-configure the first slice identifier and the association relationship.
  • the access and mobility management network element can send the association relationship and the first slice identifier to the terminal; accordingly, the terminal can receive the self-access link. Enter the association relationship with the mobility management network element and the first slice identifier.
  • the first slice identifier sent by the access and mobility management network element to the terminal, or the first slice identifier received by the terminal from the access and mobility management network element can be carried in the URSP of the terminal, or That is, it can be carried in existing cells to reduce implementation difficulty, or it can also be carried in new cells to improve implementation flexibility, without limitation.
  • the access and mobility management network element can obtain the association relationship from the policy control network element or the network slicing selected network element in advance, or can also obtain the association relationship from any other possible network element, or the association relationship can be pre-configured locally. Specifically, You can also refer to the relevant introduction in the above S500 and will not go into details.
  • the difference between method 1 and method 2 is that for method 1, since the slice identifier of a certain service in other networks (networks other than the first network and the second network) may be the same as the second slice identifier, That is to say, the second slice identifier is a non-unique identifier. Therefore, the access and mobility management network element can provide the terminal with the identifier of the second network to distinguish these same slice identifiers to ensure that the terminal can finally determine the second slice identifier. , rather than the slice identifier of other networks.
  • the access and mobility management network element may also send a list of allowed first slice identifiers to the terminal to authenticate the first slice identifier.
  • the specific implementation of Mode 1 and Mode 2 can also refer to the relevant introductions in S701-S703 above, and will not be described again.
  • the association relationship may be an association relationship between the first slice identifier, the second slice identifier, and the identifier of the second network.
  • the terminal may query the association relationship based on the second slice identifier, the identifier of the second network, and the association relationship, such as using the second slice identifier and the identifier of the second network, to conveniently determine the third slice identifier associated with the second slice identifier and the identifier of the second network. All slice identifiers are used, that is, the terminal determines the first slice identifier to simplify the implementation complexity of access and mobility management network elements and reduce the overhead on the network side.
  • the terminal may locally pre-configure the second slice identifier, the identifier of the second network, and the association relationship.
  • the access and mobility management network element may send the association relationship, the second slice identifier and the second network to the terminal. The identification; correspondingly, the terminal receives the association relationship from the access and mobility management network element, the second slice identification and the identification of the second network.
  • the second slice identifier and the identifier of the second network are sent by the access and mobility management network element to the terminal, or in other words, the second slice identifier and the identifier of the second network are received by the terminal from the access and mobility management network element.
  • the identifier can be carried in the URSP of the terminal, that is, it can be carried in existing cells to reduce the difficulty of implementation, or it can also be carried in new cells to improve implementation flexibility, without limitation. It can be understood that the way in which the access and mobility management network element obtains the association relationship is similar to the above-mentioned method 1, which can be referred to for understanding and will not be described again.
  • the association relationship may be the association relationship between the first slice identifier and the second slice identifier.
  • the terminal can query the association relationship based on the second slice identifier and the association relationship, such as using the second slice identifier, to facilitate the determination of the first slice identifier associated with the second slice identifier, that is, the terminal can determine the first slice identifier.
  • Slice identification is used to simplify the implementation complexity of access and mobility management network elements and reduce the overhead on the network side.
  • the terminal may locally pre-configure the second slice identifier and the association relationship.
  • the access and mobility management network element may send the association relationship and the identifier of the second network to the terminal; accordingly, the terminal receives the The association relationship with the mobility management network element and the identifier of the second network.
  • the second slice identifier sent by the access and mobility management network element to the terminal can be carried in the URSP of the terminal, that is, It can be carried in existing cells to reduce the difficulty of implementation, or it can be carried in new cells to improve implementation flexibility, without limitation. It can be understood that the access and mobility management network elements obtain the association relationship in the same way as The above method 2 is similar and can be understood by reference without going into details.
  • Method 3 since the second slice identifier is a non-unique identifier, the access and mobility management network element can provide the terminal with the identifier of the second network to distinguish it. These same slice identifiers ensure that the terminal can ultimately determine the first slice identifier instead of the slice identifiers of other networks.
  • the second slice identifier is a unique identifier, the access and mobility management network element may not provide an association between the network and the slice identifier, so as to save overhead and improve communication efficiency.
  • the terminal determines the first slice identifier, it may not consider the identifier of the second network, so that the processing logic is simpler.
  • the access and mobility management network element may also send a list of allowed second slice identifiers to the terminal to authenticate the second slice identifier.
  • the specific implementation of Mode 3 and Mode 4 can also refer to the relevant introductions in S801-S803 above, and will not be described again.
  • the access and mobility management network element determines the second session management network element in the second network according to the slice identifier associated with the first service.
  • the slice identifier associated with the first service is the first slice identifier.
  • the access and mobility management network element can determine the second session management network element based on the first slice identifier. This ensures that the second session management network element can support the slice corresponding to the first service.
  • the access and mobility management network element may determine the second slice identifier of the first service in the second network and the identifier of the second network based on the first slice identifier.
  • the association relationship is an association relationship between the first slice identifier, the second slice identifier, and the identifier of the second network.
  • the access and mobility management network element can determine the second slice identifier and the identifier of the second network based on the first slice identifier and the association relationship.
  • the access and mobility management network element may use the first slice identifier to query the association relationship to facilitate the determination of the second slice identifier and the identifier of the second network associated with the first slice identifier.
  • the access and mobility management network element may determine the second session management network element according to the second slice identifier and the identifier of the second network. It can be understood that since the slice identifier of a certain service in other networks (networks other than the first network and the second network) may be the same as the second slice identifier, that is, the second slice identifier is a non-unique identifier, so access and mobility The management network element can use the identifier of the second network to distinguish these same slice identifiers to ensure that the second session management network element within the second network can be selected instead of the session management network element of other networks.
  • the access and mobility management network element may determine the second slice identifier of the first service in the second network based on the first slice identifier.
  • the association relationship is an association relationship between the first slice identifier and the second slice identifier.
  • the access and mobility management network element can determine the second slice identifier based on the first slice identifier and the association relationship.
  • the access and mobility management network element can use the first slice identifier to query the association relationship to facilitate the determination of the second slice identifier associated with the first slice identifier. Thereafter, the access and mobility management network element can determine the second session management network element according to the second slice identifier.
  • the second identifier is a unique identifier
  • the access and mobility management network element can also determine the first slice list (such as the above S- The NSSAI list 1) contains the first slice identifier.
  • the slice identifier in the first slice list is the slice identifier of the home network of the service deployed by the second network.
  • the access and mobility management network element can determine that the slice identifier is the slice identifier that maps services deployed in other networks to the home network, so that the session management network element located in the other network can be correctly selected.
  • the access and mobility management network element can also determine the first session management network element in the home network (such as the above-mentioned SMF1) according to the first slice identifier.
  • the first session management network element can be used to establish the terminal to The user plane connection of the PSA of the second network ensures that the terminal can access the first service through the PSA.
  • the slice identifier associated with the first service is the second slice identifier.
  • the access and mobility management network element may determine the second session management network element based on the second slice identifier and the identifier of the second network. That is, since the slice identifier of a certain service in other networks (networks other than the first network and the second network) may be the same as the second slice identifier, the access and mobility management network element can use the identifier of the second network to distinguish these same slice identifiers to ensure that the second session management network element in the second network can be selected instead of the session management network element of other networks.
  • access and mobility management The network element may determine the second session management network element according to the second slice identifier. That is, if the second slice identifier is a unique identifier, the access and mobility management network element may not consider the identifier of the second network when selecting the second session management network element, so that the processing logic is simpler.
  • the access and mobility management network element can also determine that the second slice list (such as the above S-NSSAI list 2) contains the second session management network element.
  • the second slice list (such as the above S-NSSAI list 2) contains the second session management network element.
  • Slice ID the slice identifier in the second slice list is the slice identifier of the service deployed in the second network in the second network.
  • the access and mobility management network element can determine that the slice identifier is the slice identifier of the service deployed in other networks in order to correctly select the session management network element located in the other network.
  • the access and mobility management network element can also determine the first session management network element in the home network based on the second slice identifier.
  • the first session management network element can be used to establish a PSA from the terminal to the second network.
  • User plane connection ensures that the terminal can access the first service through the PSA.
  • the access and mobility management network element may determine the first slice identifier based on the second slice identifier and the identifier of the second network. That is, if the second slice identifier is a non-unique identifier, the access and mobility management network element can use the identifier of the second network to distinguish these same slice identifiers to ensure that the first slice identifier can be finally determined. rather than the slice identifier of other networks.
  • the association relationship is an association relationship between the first slice identifier, the second slice identifier, and the identifier of the second network.
  • the access and mobility management network element may query the association relationship based on the second slice identifier, the identifier of the second network, and the association relationship, such as using the second slice identifier and the identifier of the second network, to facilitate determination of the association relationship with the second slice identifier and the second network identifier.
  • the two network identifiers are associated with the first slice identifier. Then, the access and mobility management network element can determine the first session management network element according to the first slice identifier.
  • the access and mobility management network element may determine the first slice identifier based on the second slice identifier. That is, if the second slice identifier is a unique identifier, the access and mobility management network element may not consider the identifier of the second network when determining the first slice identifier, so that the processing logic is simpler.
  • the association relationship is the association relationship between the first slice identifier and the second slice identifier.
  • the access and mobility management network element may query the association relationship based on the second slice identifier and the association relationship, such as using the second slice identifier, to conveniently determine the first slice identifier associated with the second slice identifier. Then, the access and mobility management network element can determine the first session management network element according to the first slice identifier.
  • the slice identifier associated with the first service includes a first slice identifier and a second slice identifier.
  • the access and mobility management network element can determine the first session management network element based on the first slice identifier.
  • the access and mobility management network element may determine the second session management network element based on the second slice identifier and the identifier of the second network; or, the access and mobility management network element may determine the second session management network element based on the second slice identifier.
  • the second session management network element that is, if the second slice identifier is a unique identifier, the access and mobility management network element may not consider the identifier of the second network when determining the second session management network element, thereby processing logical changes. Simple.
  • the first session management network element can be used to establish a user plane connection from the terminal to the PSA, thus ensuring that the terminal can access through the PSA.
  • the access and mobility management network element sends a session establishment acceptance message to the terminal.
  • the terminal receives the session establishment accept message from the access and mobility management network element.
  • the session establishment acceptance message is used to indicate that the second network has established a session for the terminal to access the first service.
  • S506-S512 For details, please refer to the relevant introduction of S506-S512 above, which will not be described again.
  • the access and mobility management network element of the home network can select the first service for the first service based on the slice identifier associated with the first service.
  • the second session management network element in the second network so that the second session management network element can establish a session of the first service for the terminal, such as selecting the session anchor point of the first service in the second network, such as the protocol data unit session anchor point PSA , so that the terminal can access the first service through the PSA, so that the terminal accessing the home network can still access services deployed on other operator networks.
  • the first service is a service that needs to be accessed through the session anchor point of the second network, it can be further implemented that when the service does not support PSA access of other operators, other operators, such as the home network The terminal can still access the service.
  • FIG. 10 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 1000 includes: a transceiver module 1001 and a processing module 1002.
  • FIG. 10 shows only the main components of the communication device.
  • the communication device 1000 may be adapted to the communication system shown in FIG. 4 to perform the functions of the above-mentioned AMF or access and mobility management network element.
  • the transceiving module 1001 can be used to perform the function of sending and receiving messages by the AMF or the access and mobility management network element, such as the functions in the above-mentioned steps S504, S506, S901 and so on.
  • the processing module 1002 may perform functions of the AMF or access and mobility management network element other than sending and receiving messages, such as the functions in the above steps S505, S902 and so on.
  • the transceiver module 1001 is used to receive a session establishment request message from the terminal.
  • the communication device 1000 is deployed on a first network, the first network is the home network of the terminal, and the terminal accesses the home network.
  • the session establishment request message includes a slice identifier associated with the first service deployed on the second network, which is a network other than the home network.
  • the processing module 1002 is configured to determine a second session management network element in the second network based on the slice identifier.
  • the second session management network element is used to establish a session for the terminal to access the first service.
  • the transceiver module 1001 may include a sending module and a receiving module.
  • the sending module is used to realize the sending function of the communication device 1000
  • the receiving module is used to realize the receiving function of the communication device 1000.
  • the communication device 1000 may also include a storage module that stores programs or instructions.
  • the processing module 1002 executes the program or instruction, the communication device 1000 can perform the above communication method.
  • the communication device 1000 may be a network device, a chip (system) or other components or components that can be disposed in the network device, or a device including a network device, which is not limited in this application.
  • the technical effects of the communication device 1000 can be referred to the technical effects of the above communication method, which will not be described again here.
  • the communication device 1000 may be adapted to the communication system shown in FIG. 4 to perform the above-mentioned functions of the UE or terminal.
  • the transceiver module 1001 can be used to perform the function of the UE or terminal to send and receive messages, such as the functions in the above-mentioned steps S502, S504, S901 and so on.
  • the processing module 1002 may perform functions of the UE or terminal other than sending and receiving messages, such as the functions in the above-mentioned S503 and other steps. For example,
  • the processing module 1002 is used to control the transceiver module 1001 to send a session establishment request message to the access and mobility management network element.
  • the access and mobility management network element is deployed on the first network
  • the first network is the home network of the communication device 1000
  • the communication device 1000 accesses the home network
  • the session establishment request message includes the first service association deployed with the second network.
  • the slice identifies that the second network is a network other than the home network.
  • the transceiver module 1001 is used to receive a session establishment accept message from the access and mobility management network element, where the session establishment accept message is used to indicate that the second network has established a session for the communication device 1000 to access the first service. session.
  • the transceiver module 1001 may include a sending module and a receiving module.
  • the sending module is used to realize the sending function of the communication device 1000
  • the receiving module is used to realize the receiving function of the communication device 1000.
  • the communication device 1000 may also include a storage module that stores programs or instructions.
  • the processing module 1002 executes the program or instruction, the communication device 1000 can perform the above communication method.
  • the communication device 1000 may be a terminal, a chip (system) or other components or components that can be installed in the terminal, or a device including terminal equipment, which is not limited in this application.
  • the technical effects of the communication device 1000 can be referred to the technical effects of the above communication method, which will not be described again here.
  • FIG. 11 is a second structural schematic diagram of a communication device provided by an embodiment of the present application.
  • the communication device may be a terminal, or a chip (system) or other components or components that can be installed in the terminal.
  • the communication device 1100 may include a processor 1101 .
  • the communication device 1100 may also include a memory 1102 and/or a transceiver 1103.
  • the processor 1101 is coupled to the memory 1102 and the transceiver 1103, for example, through a communication bus.
  • the processor 1101 is the control center of the communication device 1100, and may be a processor or a collective name for multiple processing elements.
  • the processor 1101 is one or more central processing units (CPUs), may also be an application specific integrated circuit (ASIC), or may be configured to implement the implementation of the present application.
  • One or more integrated circuits such as one or more microprocessors (digital signal processor, DSP), or one or more field programmable gate arrays (field programmable gate array, FPGA).
  • the processor 1101 can perform various functions of the communication device 1100 by running or executing software programs stored in the memory 1102 and calling data stored in the memory 1102, for example, performing the functions shown in FIGS. 8-10 above. communication method.
  • the processor 1101 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 11 .
  • the communication device 1100 may also include multiple processors, such as the processor 1101 and the processor 1104 shown in FIG. 11 .
  • processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU).
  • a processor here may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the memory 1102 is used to store the software program for executing the solution of the present application, and is controlled by the processor 1101 for execution.
  • the memory 1102 is used to store the software program for executing the solution of the present application, and is controlled by the processor 1101 for execution.
  • the memory 1102 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory (RAM)) or a random access memory (RAM) that can store information and instructions.
  • ROM read-only memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • RAM random access memory
  • Other types of dynamic storage devices for instructions can also be electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical discs Storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store desired program code in the form of instructions or data structures and any other media capable of being accessed by a computer, without limitation.
  • the memory 1102 may be integrated with the processor 1101, or may exist independently, and be coupled with the processor 1101 through the interface circuit of the communication device 1
  • the communication device 1100 is a terminal, and the transceiver 1103 can be used to communicate with a network device or with another terminal device.
  • the communication device 1100 is a network device, and the transceiver 1103 can be used to communicate with a terminal or another network device.
  • the transceiver 1103 may include a receiver and a transmitter (not shown separately in Figure 11). Among them, the receiver is used to implement the receiving function, and the transmitter is used to implement the sending function.
  • the transceiver 1103 may be integrated with the processor 1101, or may exist independently and be coupled to the processor 1101 through the interface circuit (not shown in Figure 11) of the communication device 1100. This is not the case in the embodiment of this application. Specific limitations.
  • the structure of the communication device 1100 shown in Figure 11 does not constitute a limitation on the communication device.
  • the actual communication device may include more or less components than shown in the figure, or some components may be combined, or Different component arrangements.
  • the technical effects of the communication device 1100 can be referred to the technical effects of the communication method described in the above method embodiments, which will not be described again here.
  • An embodiment of the present application provides a communication system.
  • the communication system may include: UE, AMF, SMF1, SMF2, UPF, and/or PSA shown in Figures 5 to 8, etc. These network elements are used to cooperate in executing the tasks shown in any of the figures in Figures 5 to 8. method flow.
  • the communication system may include: the terminal and/or the access and mobility management network element shown in Figure 9, and these network elements are used to cooperate in executing the method flow shown in Figure 9.
  • the processor in the embodiment of the present application can be a central processing unit (CPU).
  • the processor can also be other general-purpose processors, digital signal processors (DSP), special-purpose integrated processors, etc.
  • Circuit application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory. Volatile memory may be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous DRAM
  • SDRAM double data rate synchronous dynamic random access memory
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM enhanced synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM, DR RAM
  • the above embodiments may be implemented in whole or in part by software, hardware (such as circuits), firmware, or any other combination.
  • the above-described embodiments may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmit to another website, computer, server or data center through wired (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that a computer can access, or a data storage device such as a server or a data center that contains one or more sets of available media.
  • the usable media may be magnetic media (eg, floppy disk, hard disk, tape), optical media (eg, DVD), or semiconductor media.
  • the semiconductor medium may be a solid state drive.
  • At least one refers to one or more, and “plurality” refers to two or more.
  • At least one of the following” or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items).
  • at least one of a, b, or c can mean: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple .
  • the size of the sequence numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic, and should not be used in the embodiments of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a
  • the storage medium includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente demande se rapporte au domaine technique des communications, concerne un procédé et un appareil de communication, et est utilisée pour réaliser qu'un terminal accédant à un réseau domestique peut toujours accéder à des services déployés dans d'autres réseaux d'opérateur. Dans le procédé, lorsqu'un premier service est déployé dans un deuxième réseau et que le terminal accède au réseau domestique, un élément de réseau de gestion d'accès et de mobilité du réseau domestique peut sélectionner un deuxième élément de réseau de gestion de session dans le deuxième réseau pour le premier service sur la base d'un identifiant de tranche associé au premier service, de telle sorte que le deuxième élément de réseau de gestion de session peut établir une session du premier service pour le terminal, par exemple, sélectionner un ancrage de session du premier service dans le deuxième réseau, tel qu'un ancrage de session d'unité de données de protocole (PSA), de telle sorte que le terminal peut accéder au premier service au moyen du PSA, ce qui permet de réaliser que le terminal accédant au réseau domestique peut toujours accéder aux services déployés dans d'autres réseaux d'opérateur.
PCT/CN2023/104208 2022-07-13 2023-06-29 Procédé et appareil de communication WO2024012230A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210822414.7 2022-07-13
CN202210822414.7A CN117440356A (zh) 2022-07-13 2022-07-13 通信方法及装置

Publications (1)

Publication Number Publication Date
WO2024012230A1 true WO2024012230A1 (fr) 2024-01-18

Family

ID=89535504

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/104208 WO2024012230A1 (fr) 2022-07-13 2023-06-29 Procédé et appareil de communication

Country Status (2)

Country Link
CN (1) CN117440356A (fr)
WO (1) WO2024012230A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108684073A (zh) * 2017-06-19 2018-10-19 华为技术有限公司 一种注册及会话建立的方法、终端和amf实体
CN110519806A (zh) * 2018-05-21 2019-11-29 华为技术有限公司 切换方法、设备及系统
US20200053636A1 (en) * 2017-03-21 2020-02-13 Telefonaktiebolaget Lm Ericsson (Publ) SMF Selection Based On Supported DNN
CN114342549A (zh) * 2019-11-07 2022-04-12 Oppo广东移动通信有限公司 用于连接网络的方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200053636A1 (en) * 2017-03-21 2020-02-13 Telefonaktiebolaget Lm Ericsson (Publ) SMF Selection Based On Supported DNN
CN108684073A (zh) * 2017-06-19 2018-10-19 华为技术有限公司 一种注册及会话建立的方法、终端和amf实体
CN110519806A (zh) * 2018-05-21 2019-11-29 华为技术有限公司 切换方法、设备及系统
CN114342549A (zh) * 2019-11-07 2022-04-12 Oppo广东移动通信有限公司 用于连接网络的方法和设备

Also Published As

Publication number Publication date
CN117440356A (zh) 2024-01-23

Similar Documents

Publication Publication Date Title
WO2023284584A1 (fr) Procédé et appareil de communication
WO2021057794A1 (fr) Procédé de configuration de service, dispositif de communication et système de communication
WO2023280121A1 (fr) Procédé et appareil d'obtention de service de périphérie
WO2022048394A1 (fr) Procédé de connexion réseau, procédé de déconnexion réseau et appareil de communication
WO2022033558A1 (fr) Procédé de gestion de relais et appareil de communication
WO2021135650A1 (fr) Procédé et appareil de communication
WO2022033543A1 (fr) Procédé de communication de relais, et appareil de communication
WO2022222745A1 (fr) Procédé et appareil de communication
WO2022199451A1 (fr) Procédé et appareil de commutation de session
WO2022222817A1 (fr) Procédé et appareil de sélection de serveur d'application d'extrémité
WO2022194262A1 (fr) Procédé et appareil de communication de sécurité
WO2023284551A1 (fr) Procédé, dispositif et système de communication
WO2022170798A1 (fr) Procédé de détermination de stratégie et appareil de communication
WO2024012230A1 (fr) Procédé et appareil de communication
WO2022067736A1 (fr) Procédé et appareil de communication
WO2024051313A1 (fr) Procédé, appareil et système de gestion de ressources de communication, et support d'enregistrement
WO2023143212A1 (fr) Procédé et appareil de communication
WO2023207637A1 (fr) Procédé et appareil de communication
WO2023213215A1 (fr) Procédé et appareil de communication
WO2023051381A1 (fr) Procédé et appareil de détermination de serveur d'application
WO2023066207A1 (fr) Procédé et appareil de communication
WO2023197737A1 (fr) Procédé d'envoi de message, procédé de gestion de pin, appareil de communication et système de communication
CN117528462B (zh) 一种多网络组网实现的工业物联网的数据传输方法
WO2023056852A1 (fr) Procédé, appareil et système de communication
WO2023116560A1 (fr) Procédé et appareil de communication

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: 23838722

Country of ref document: EP

Kind code of ref document: A1