WO2023077948A1 - 一种通信的方法和装置 - Google Patents

一种通信的方法和装置 Download PDF

Info

Publication number
WO2023077948A1
WO2023077948A1 PCT/CN2022/117164 CN2022117164W WO2023077948A1 WO 2023077948 A1 WO2023077948 A1 WO 2023077948A1 CN 2022117164 W CN2022117164 W CN 2022117164W WO 2023077948 A1 WO2023077948 A1 WO 2023077948A1
Authority
WO
WIPO (PCT)
Prior art keywords
request
terminal device
pdu session
redundancy
identifier
Prior art date
Application number
PCT/CN2022/117164
Other languages
English (en)
French (fr)
Inventor
谢春生
丁辉
周凯
韩文勇
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023077948A1 publication Critical patent/WO2023077948A1/zh

Links

Images

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/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data

Definitions

  • the embodiments of the present application relate to the communication field, and, more specifically, relate to a communication method and device.
  • the redundant transmission of multi-user equipment is completed through user subscription, that is, the redundant transmission relationship of the subscriber identity module (subscriber identity module, SIM) issued to the user is relatively fixed.
  • SIM subscriber identity module
  • users In the process of using SIM cards, users must keep in mind the redundant contract relationship between the two SIM cards, and it is not allowed to mix with other SIM cards. Therefore, in order to ensure the reliability of redundant transmission, each user will have a non-redundant transmission SIM card and a redundant transmission SIM card at the same time, and redundant transmission through static subscription.
  • Embodiments of the present application provide a communication method and device, which can realize redundant transmission of equipment under the condition that the terminal equipment is decoupled from the subscriber.
  • a communication method is provided, and the method is applied to an SMF, or may also be executed by a chip or a circuit configured in the SMF, which is not limited in the present application.
  • the method includes: a session management function network element SMF receives a first PDU session request from a first terminal device and a second PDU session request from a second terminal device, wherein the first PDU session request and the second PDU session request The session request carries the same redundant transmission configuration information; the SMF sends a request to create a first PDU session context and a request to create a second PDU session context to the user plane functional entity UPF, and the request to create a first PDU session context and the create The second PDU session context request carries the redundant transmission configuration information; the SMF receives a first response message and a second response message from the UPF, and the first response message carries the PDU session of the first terminal device An identifier, where the second response message carries the PDU session identifier of the second terminal device.
  • the SMF obtains redundant transmission configuration information through the PDU session request of the terminal device.
  • the terminal device and the subscriber can In the case of decoupling, redundant transmission of devices is realized, and there is no need to initiate a separate redundant transmission session process, which can save resources.
  • the method before the SMF sends a request to create a first PDU session context and a request to create a second PDU session context to the user plane functional entity UPF, the method further includes: The SMF sends a first request message to the UPF, where the first request message is used to request to create a redundant transmission context for the first terminal device and the second terminal device; the SMF receives a message from the UPF A response message to the first request, the response message to the first request includes a redundant transmission context identifier, wherein the request to create a first PDU session context and the request to create a second PDU session context also carry the Redundant transport context identifier.
  • the SMF sends a first request to the UPF to create a redundant context, and the UPF creates the same redundant context for the terminal equipment for redundant transmission, so as to achieve the purpose of redundant transmission.
  • the method further includes: the SMF determines the UPF for the first terminal device and the second terminal device according to the redundancy configuration information .
  • the SMF sends the first modification request of the first terminal device and the second modification request of the second terminal device to the UPF, and the The first modification request message carries the PDU session identifier of the first terminal device, the second modification request carries the PDU session identifier of the second terminal device, and the first modification request is used to indicate that the first terminal device
  • the PDU session identifier of the device is added to the redundant transmission context, and the second modification request is used to indicate that the PDU session identifier of the second terminal device is added to the redundant transmission context.
  • the redundant transmission configuration information includes: redundancy indication information, redundancy type, and redundancy identification, and the redundancy indication information is used to indicate that redundancy is enabled. transmission.
  • the redundancy type and the redundancy identifier are set by a user.
  • the method further includes:
  • the SMF sends a first delete message and a second delete message to the UPF, the first delete message is used to indicate the deletion of the PUD session context, and the second delete message is used to indicate the deletion of the redundant transmission context
  • the user signs up to identify and/or delete said redundant transmission context.
  • the resource of the system can be saved by deleting the information to delete the PDU session context or deleting the user subscription identifier or the redundant transmission context of a certain terminal device in the redundant transmission context.
  • a communication method is provided, and the method is applied to an SMF, or may also be executed by a chip or a circuit configured in the SMF, which is not limited in the present application.
  • the method includes: a session management function network element SMF receives a first PDU session request from a first terminal device, and a second PDU session request from a second terminal device;
  • the UDM obtains the first redundant transmission configuration information of the first terminal device, and the SMF obtains the second redundant transmission configuration information of the second terminal device from the UDM according to the second PDU session request;
  • the SMF sends a request to create a first PDU session context and a request to create a second PDU session context to the user plane functional entity UPF, the request to create a first PDU session context carries the first redundant transmission configuration information, and the request to create a second PDU session context
  • Two PDU session context requests carry the second redundant transmission configuration information;
  • the SMF receives a first response message and a second response message from the UPF, and the
  • SMF obtains the redundant transmission configuration information of the terminal equipment from UDM, and sends the redundant transmission configuration information to UPF through creating a PDU session process, which saves resources and realizes the redundant transmission of terminal equipment and user subscription information. Decoupling.
  • the method before the SMF sends a request to create a first PDU session context and a request to create a second PDU session context to the user plane functional entity UPF, the method further includes: The SMF sends a first request message to the UPF, where the first request message is used to request to create a redundant transmission context for the first terminal device and the second terminal device; the SMF receives a message from the UPF A response message to the first request, the response message to the first request includes a redundant transmission context identifier, wherein the request to create a first PDU session context and the request to create a second PDU session context also carry the Redundant transport context identifier.
  • the SMF sends the first modification request of the first terminal device and the second modification request of the second terminal device to the UPF
  • the The first modification request message carries the PDU session identifier of the first terminal device
  • the second modification request carries the PDU session identifier of the second terminal device
  • the first modification request is used to indicate that the first terminal device
  • the PDU session identifier of the device is added to the redundant transmission context
  • the second modification request is used to indicate that the PDU session identifier of the second terminal device is added to the redundant transmission context.
  • the first redundant transmission configuration information includes: a redundancy type, a redundancy identifier, and subscription redundancy indication information of the first terminal
  • the first The two-redundancy transmission configuration information includes: the redundancy type, the redundancy identifier, and the subscription redundancy indication information of the second terminal.
  • the redundancy type and the redundancy identifier are set by an application function network element AF.
  • the method further includes: the SMF sends a first deletion message and a second deletion message to the UPF, the first deletion message is used to indicate deletion For the PUD session context, the second deletion message is used to instruct to delete the user subscription identifier in the redundant transmission context and/or delete the redundant transmission context.
  • a communication method is provided, and the method is applied to an AMF, or may also be executed by a chip or a circuit configured in the AMF, which is not limited in the present application.
  • the method includes: the access and mobility management function network element AMF receives a first PDU session request from a first terminal device and a second PDU session request from a second terminal device, wherein the first PDU session request and the The second PDU session request carries the same redundant transmission configuration information; the AMF determines the same session management function network element SMF for the first terminal device and the second terminal device according to the redundant transmission configuration information; The AMF sends the first PDU session request and the second PDU session request to the SMF.
  • the AMF selects the same SMF for different terminal devices through the redundant transmission configuration information sent by the terminal device to implement redundant transmission, which improves the performance of the system.
  • the redundant transmission configuration information includes: redundancy indication information, redundancy type, and redundancy identification, and the redundancy indication information is used to indicate that redundancy is enabled transmission, wherein the AMF determines the same SMF for the first terminal device and the second terminal device according to the redundant transmission configuration information, including: the AMF identifies the first The terminal device and the second terminal device determine the same SMF.
  • a communication method is provided, and the method is applied to an AMF, or may also be executed by a chip or a circuit configured in the AMF, which is not limited in the present application.
  • the method includes: access and mobility management function network element AMF receives a first PDU session request from a first terminal device and a second PDU session request from a second terminal device; the AMF receives the first PDU session request according to the first PDU session request Obtain the first redundant transmission configuration information of the first terminal device from the unified data management UDM, and the AMF obtains the second redundant transmission configuration information of the second terminal device from the UDM according to the second PDU session request Transmission configuration information; the AMF determines the same session management function network element SMF for the first terminal device and the second terminal device according to the first redundant transmission configuration information and the second redundant transmission configuration information ; The AMF sends the first PDU session request and the second PDU session request to the SMF.
  • AMF obtains terminal equipment redundant transmission configuration information from UDM to select the same SMF for different terminal equipment to realize redundant transmission, which improves system performance.
  • the first redundant transmission configuration information includes: redundancy type, redundancy identifier, and subscription redundancy indication information of the first terminal
  • the second The two redundant transmission configuration information includes: the redundancy type, the redundancy identifier, and the subscription redundancy indication information of the second terminal, wherein the AMF according to the first redundant transmission configuration information and the The second redundant transmission configuration information determines the same SMF for the first terminal device and the second terminal device, including: the AMF assigns the first terminal device and the second terminal device according to the redundancy identifier. The devices determine the same SMF.
  • a communication method is provided, and the method is applied to an AF, or may also be executed by a chip or a circuit configured in the AF, which is not limited in the present application.
  • the method includes: an application function entity AF acquires first configuration information; the AF sends a redundancy configuration request message to a network opening function entity NEF based on the first configuration information, and the redundancy configuration request message includes first indication information or Second indication information, where the first indication information is used to instruct the NEF to add the first redundant configuration information, and the second indication information is used to instruct the NEF to delete the second redundant configuration information.
  • the AF sends a redundancy configuration request message to a network opening functional entity NEF based on the first configuration information, including: the AF determines that the first terminal device and The subscriber of the first terminal device is bound for the first time, and the second terminal device is bound with the subscriber of the second terminal device for the first time; the AF sends a redundant configuration request message to the NEF, and the The redundancy configuration request message includes first indication information, and the first redundancy configuration information includes: the user subscription identifier of the first terminal device, the user subscription identifier of the second terminal device, redundancy indication information, redundancy A type and a redundancy identifier, the redundancy indication information is used to indicate to enable redundant transmission.
  • the AF sends a redundancy configuration request message to a network opening functional entity NEF based on the first configuration information, including: the AF determines that the first terminal device and The subscriber of the first terminal device is not bound for the first time, and the second terminal device is not bound with the subscriber of the second terminal device for the first time; the AF sends a redundant configuration request message to the NEF, including The second indication information, the second redundancy configuration information includes: the user subscription identifier of the first terminal device, the user subscription identifier of the second terminal device, and a redundancy identifier.
  • the first configuration information includes a redundancy type, a device identifier of the first terminal device, a subscriber identifier of the first terminal device, the The device identifier of the second terminal device, and the subscriber identifier of the second terminal device.
  • a communication method is provided, and the method is applied to a NEF, or may also be executed by a chip or a circuit configured in the NEF, which is not limited in the present application.
  • the method includes: a network opening function entity NEF receives a redundancy configuration request message from an application function entity AF, where the redundancy configuration request message includes first indication information or second indication information, wherein the first indication information is used for indicating to add the first redundant configuration information of at least two terminal devices, the second indicating information is used to indicate to delete the second redundant configuration information; the NEF sends the modification to the unified data management UDM according to the redundant configuration request message Sign up for data requests.
  • the redundant configuration request message includes first indication information
  • the NEF sends a request to modify the subscription data to the unified data management UDM according to the redundant configuration request message, including: the NEF
  • the first indication information sends a subscription data modification request to the UDM, where the subscription data modification request is used to instruct the UDM to add the first redundant configuration information.
  • the first redundancy configuration information includes: a user subscription identifier of the first terminal device, a user subscription identifier of the second terminal device, a redundancy indication information, a redundancy type, and a redundancy identifier, and the redundancy indication information is used to instruct starting redundant transmission.
  • the redundant configuration request message when the first terminal device and the subscriber of the first terminal device are not bound for the first time, and the second terminal device and the subscriber of the second terminal device When the subscriber is not binding for the first time, the redundant configuration request message includes second indication information, and the NEF sends a request to modify the subscription data to the unified data management UDM according to the redundant configuration request message, including: the NEF
  • the second indication information sends a subscription data modification request to the UDM, where the subscription data modification request is used to instruct the UDM to delete the second redundant configuration information.
  • the second redundancy configuration information includes: the user subscription identifier of the first terminal device, the user subscription identifier of the second terminal device, and the redundancy Yu logo.
  • a communication method is provided, and the method is applied to a UPF, or may also be executed by a chip or a circuit configured in the UPF, which is not limited in the present application.
  • the method includes: a user plane function entity UPF receives a request for creating a first PDU session context and a request for creating a second PDU session context from a session management function network element SMF, the request for creating a first PDU session context and the request for creating a second PDU
  • the session context request carries redundant transmission configuration information; the UPF creates a redundant transmission context according to the redundant transmission configuration information; the UPF sends a first response message and a second response message to the SMF, and the first response
  • the message carries the PDU session identifier of the first terminal device, and the second response message carries the PDU session identifier of the second terminal device.
  • the method further includes: the UPF creates a first PDU session context for the first terminal device according to the first PDU session context request, and according to the The second PDU session context request creates a second PDU session context for the second terminal device.
  • the method further includes: the UPF adding the PDU session identifier of the first terminal device to the redundant transmission context, and the UPF adding The PDU session identifier of the second terminal device is added to the redundant transmission context.
  • a communication method is provided, and the method is applied to a UPF, or may also be executed by a chip or a circuit configured in the UPF, which is not limited in the present application.
  • the method includes: a user plane functional entity UPF receives a first request message from a session management function network element SMF, and the first request message is used to request to create redundant transmission for the first terminal device and the second terminal device Context; the UPF creates a redundant transmission context according to the redundant transmission configuration information; the UPF sends a first request response message to the SMF, and the first request response message includes a redundant transmission context identifier.
  • the method further includes: the UPF receives a request for creating a first PDU session context and a request for creating a second PDU session context from a session management function network element SMF; The UPF sends a first response message and a second response message to the SMF, the first response message carries the PDU session identifier of the first terminal device, and the second response message carries the PDU session identifier of the second terminal device PDU session identifier.
  • the method further includes: the UPF creates a first PDU session context for the first terminal device according to the first PDU session context request, and according to the The second PDU session context request creates a second PDU session context for the second terminal device.
  • the method further includes: the UPF receiving the first modification request from the SMF and the second modification request from the second terminal device, the The first modification request message carries the PDU session identifier of the first terminal device, and the second modification request carries the PDU session identifier of the second terminal device; The PDU session identifier of the terminal device is added to the redundant transmission context, and the UPF adds the PDU session identifier of the second terminal device to the redundant transmission context according to the second modification request.
  • a communication device including a functional module for implementing the method in any possible implementation manner of the foregoing first aspect or the second aspect.
  • a communication device including a functional module for implementing the method in any possible implementation manner of the aforementioned third aspect or fourth aspect.
  • a communication device including a functional module for implementing the method in any possible implementation manner of the foregoing fifth aspect.
  • a communication device including a functional module for implementing the method in any possible implementation manner of the foregoing sixth aspect.
  • a thirteenth aspect provides a communication device, including a functional module for implementing the method in any possible implementation manner of the foregoing seventh or eighth aspect.
  • a communication device including a processor and an interface circuit, and the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or transmit signals from the processor Sending to other communication devices other than the communication device, the processor implements the method in any possible implementation manner of the aforementioned first aspect or second aspect through a logic circuit or executing code instructions.
  • a communication device including a processor and an interface circuit, and the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or transmit signals from the processor The signal is sent to other communication devices other than the communication device, and the processor implements the method in any possible implementation manner of the aforementioned third aspect or fourth aspect through a logic circuit or executing code instructions.
  • a communication device including a processor and an interface circuit, and the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or transmit signals from the processor The signal is sent to other communication devices other than the communication device, and the processor implements the method in any possible implementation manner of the foregoing fifth aspect through a logic circuit or by executing code instructions.
  • a communication device including a processor and an interface circuit, the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or transmit signals from the processor The signal is sent to other communication devices other than the communication device, and the processor implements the method in any possible implementation manner of the foregoing sixth aspect through a logic circuit or by executing code instructions.
  • a communication device including a processor and an interface circuit, and the interface circuit is used to receive signals from other communication devices other than the communication device and transmit them to the processor or transmit signals from the processor The signal is sent to other communication devices other than the communication device, and the processor implements the method in any possible implementation manner of the foregoing seventh or eighth aspect through a logic circuit or by executing code instructions.
  • a computer-readable storage medium in which computer programs or instructions are stored, and when the computer programs or instructions are executed, any of the aforementioned first or second aspects can be realized. method in a possible implementation.
  • a computer-readable storage medium in which a computer program or instruction is stored, and when the computer program or instruction is executed, any of the aforementioned third or fourth aspects can be realized. method in a possible implementation.
  • a computer-readable storage medium is provided, and a computer program or instruction is stored in the computer-readable storage medium, and when the computer program or instruction is executed, any possible implementation of the aforementioned fifth aspect is realized methods in methods.
  • a computer-readable storage medium is provided, and a computer program or instruction is stored in the computer-readable storage medium, and when the computer program or instruction is executed, any possible implementation of the aforementioned sixth aspect is realized methods in methods.
  • a computer-readable storage medium is provided, and a computer program or instruction is stored in the computer-readable storage medium.
  • the computer program or instruction is executed, the aforementioned seventh or eighth aspect is realized.
  • a computer program product including instructions is provided, and when the instructions are executed, the method in any possible implementation manner of the aforementioned first aspect or second aspect is implemented.
  • a twenty-fifth aspect provides a computer program product containing instructions. When the instructions are executed, the method in any possible implementation manner of the aforementioned third aspect or fourth aspect is implemented.
  • a computer program product containing instructions is provided, and when the instructions are executed, the method in any possible implementation manner of the aforementioned fifth aspect is implemented.
  • a computer program product containing instructions is provided, and when the instructions are executed, the method in any possible implementation manner of the aforementioned sixth aspect is implemented.
  • a twenty-eighth aspect provides a computer program product containing instructions. When the instructions are executed, the method in any possible implementation manner of the aforementioned seventh or eighth aspect is implemented.
  • a twenty-ninth aspect provides a computer program.
  • the computer program includes codes or instructions. When the codes or instructions are executed, the method in any possible implementation manner of the aforementioned first aspect or second aspect is implemented.
  • a computer program in a thirtieth aspect, includes codes or instructions, and when the codes or instructions are executed, implement the method in any possible implementation manner of the aforementioned third or fourth aspect.
  • a thirty-first aspect provides a computer program, the computer program includes codes or instructions, and when the codes or instructions are executed, the method in any possible implementation manner of the aforementioned fifth aspect is implemented.
  • a thirty-second aspect provides a computer program, the computer program includes codes or instructions, and when the codes or instructions are executed, the method in any possible implementation manner of the aforementioned sixth aspect is implemented.
  • a thirty-third aspect provides a computer program, the computer program includes codes or instructions, and when the codes or instructions are executed, implement the method in any possible implementation manner of the aforementioned seventh or eighth aspect.
  • a chip system includes a processor, and may further include a memory, configured to implement the method in any possible implementation manner of the aforementioned first aspect or second aspect.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • a chip system includes a processor and may further include a memory, configured to implement the method in any possible implementation manner of the aforementioned third aspect or fourth aspect.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • a chip system includes a processor and may further include a memory, for implementing the method in any possible implementation manner of the aforementioned fifth aspect.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • a chip system includes a processor, and may further include a memory, for implementing the method in any possible implementation manner of the aforementioned sixth aspect.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • a thirty-eighth aspect provides a system-on-a-chip, where the system-on-a-chip includes a processor and may further include a memory, configured to implement the method in any possible implementation manners of the aforementioned first aspect to the eighth aspect.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • a communication system in a thirty-ninth aspect, includes any possible device in the ninth aspect to the eighteenth aspect.
  • Fig. 1 shows a schematic diagram of a communication system 100 applicable to the embodiment of the present application.
  • FIG. 2 shows a schematic diagram of a basic 5G system 200 architecture.
  • Fig. 3 shows a schematic diagram of a service-based interface architecture.
  • FIG. 4 shows a schematic flowchart of a communication method 400 provided by an embodiment of the present application.
  • FIG. 5 shows a schematic flowchart of a communication method 500 provided by an embodiment of the present application.
  • FIG. 6 shows a schematic flowchart of a communication method 600 provided by an embodiment of the present application.
  • FIG. 7 shows a schematic flowchart of a communication method 700 provided by an embodiment of the present application.
  • FIG. 8 shows a schematic flowchart of a communication method 800 provided by an embodiment of the present application.
  • FIG. 9 shows a schematic flowchart of a communication method 900 provided by an embodiment of the present application.
  • FIG. 10 is a schematic block diagram of a communication device 1000 provided by an embodiment of the present application.
  • FIG. 11 is a schematic block diagram of another communication device 1100 provided by an embodiment of the present application.
  • FIG. 1 is a schematic diagram of a communication system 100 applicable to an embodiment of the present application.
  • the communication system 100 may include at least one core network (core network, CN) network element 1200, including one or more access network devices, such as an access network device 1101, an access network device 1102, and At least one terminal device 1301 and/or terminal device 1302 .
  • the terminal device can be connected to the wireless network, so as to obtain services of the external network (such as a data network (DN)) through the wireless network, or communicate with other devices through the wireless network, such as communicating with other terminal devices.
  • the wireless network Including RAN and CN, RAN or AN is used to connect terminal equipment to the wireless network, and CN is used to manage terminal equipment and provide a gateway for communication with DN.
  • FIG. 2 shows a schematic diagram of a basic 5G system 200 architecture.
  • the system 200 includes: PCF, AMF, session management function (session management function, SMF), radio access network (radio access network, RAN), unified data management (unified data management, UDM), data network (data network, DN), user plane function (user plane function, UPF), UE, application function (application function, AF), and/or unified data repository (unified data repository, UDR).
  • the following functions may also be included in FIG. 2 (not shown in FIG. 2 ): network slice selection function (network slice selection function, NSSF), authentication server function (authentication server function, AUSF), capability exposure function (network exposure function, NEF), or network storage function (NF repository function, NRF).
  • each network element the main functions of each network element are described as follows:
  • the terminal equipment in the embodiment of the present application may be: user equipment (user equipment, UE), mobile station (mobile station, MS), mobile terminal (mobile terminal, MT), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • user equipment user equipment
  • MS mobile station
  • MT mobile terminal
  • access terminal subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
  • a terminal device may be a device that provides voice/data connectivity to users, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and the like.
  • some terminals are: mobile phone (mobile phone), tablet computer, notebook computer, palmtop computer, mobile internet device (mobile internet device, MID), wearable device, virtual reality (virtual reality, VR) device, enhanced Augmented reality (AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving or autopilot, wireless terminals in remote medical surgery, smart grid ( Wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, session initiation protocol (session initiation protocol, SIP) telephones, wireless local loop (wireless local loop, WLL) stations, personal digital assistants (personal digital assistant, PDA), handheld devices with wireless communication capabilities, computing devices, or other devices connected to wireless modems Processing devices, vehicle-mounted devices, wearable devices, terminal devices in the future 5G network or terminal devices
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices, which is a general term for the application of wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not only a hardware device, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • the terminal device may also be a terminal device in an Internet of Things (Internet of Things, IoT) system.
  • IoT Internet of Things
  • the wireless access network is an access network that realizes access network functions based on wireless communication technology.
  • the wireless access network can manage wireless resources, provide wireless access or air interface access services for terminals, and then complete the forwarding of control signals and user data between terminals and the core network.
  • the radio access network may be an evolved base station (evolved NodeB, eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (cloud radio access network, CRAN) scenario , or the access device can be a relay station, an access point, a vehicle-mounted device, a wearable device, an access device in a 5G network or an access device in a future evolved PLMN network, etc., and can be an access point in a WLAN ( The access point, AP), may be the gNB in the NR system.
  • This embodiment of this application is not limited.
  • Access and mobility management function network elements are mainly used for mobility management and access management, etc., and can be used to implement functions other than session management in mobility management entity (mobility management entity, MME) functions, for example, legal Functions such as monitoring, or access authorization (or authentication), are also used to transfer user policies between UE and PCF. In the embodiment of the present application, it can be used to implement functions of access and mobility management network elements.
  • mobility management entity mobility management entity, MME
  • legal Functions such as monitoring, or access authorization (or authentication)
  • PCF access authorization
  • it can be used to implement functions of access and mobility management network elements.
  • Session management function network elements are mainly used for session management, network interconnection protocol (internet protocol, IP) address allocation and management of terminal equipment, selection and management of user plane function (user plane function, UPF) network elements, policy control and charging functions
  • IP network interconnection protocol
  • UPF user plane function
  • the user plane functional network element can be used for packet routing and forwarding, or QoS parameter processing of user plane data, etc.
  • User data can be accessed to a data network (data network, DN) through this network element.
  • DN data network
  • it can be used to implement the functions of the user plane network element. For example, when a session is established on a different UPF, the service experience of the UE will be different. Therefore, the above-mentioned SMF is required to select a suitable UPF for the session of the UE.
  • the policy control network element is used to guide the unified policy framework of network behavior, and provide policy rule information, etc. for the control plane functional network elements (such as AMF, SMF network elements, etc.). It is mainly responsible for policy control functions such as charging for sessions and service flow levels, QoS bandwidth guarantee, mobility management, and UE policy decision-making.
  • the PCFs connected to AMF and SMF correspond to AM PCF (PCF for Access and Mobility Control) and SM PCF (PCF for Session Management) respectively, and in actual deployment scenarios, they can be the same PCF entity, or they can be Yes are two different PCF entities.
  • the network capability opening function network element is used to open the service and network capability information provided by the 3GPP network function to the outside (such as the location of the terminal, whether the session is reachable), etc.
  • the application function network element is mainly used to transmit the requirements from the application side to the network side, for example, QoS requirements or user status event subscription.
  • the AF may be a third-party functional entity, or an application service deployed by an operator, such as an IMS voice call service.
  • the application function entity of the third-party application it can also perform authorization processing through NEF when interacting with the core network.
  • the third-party application function directly sends a request message to NEF, and NEF judges whether the AF is allowed to send the request message. If passed, the request message will be forwarded to the corresponding PCF or unified data management (unified data management, UDM).
  • the unified data management network element is mainly used for unified data management, supporting authentication and trust status processing in the 3GPP authentication and key agreement mechanism, user identity processing, access authorization, registration and mobility management, subscription management, short message management, etc.
  • the unified data storage network element is mainly used for the access function of contract data, policy data, application data and other types of data.
  • the data network refers to a specific data service network accessed by the UE.
  • a typical DN includes the Internet and an IP multimedia subsystem (IP multimedia subsystem, IPMS).
  • IP multimedia subsystem IP multimedia subsystem
  • N7 The interface between PCF and SMF, which is used to deliver PDU session granularity and service data flow granularity control policies.
  • N15 the interface between the PCF and the AMF, used to issue UE policies and access control related policies.
  • N5 The interface between the AF and the PCF, used for delivering application service requests and reporting network events.
  • N4 The interface between SMF and UPF, which is used to transfer information between the control plane and the user plane, including controlling the distribution of forwarding rules, QoS control rules, and traffic statistics rules for the user plane, as well as the information reporting of the user plane.
  • N11 The interface between the SMF and the AMF, used to transfer the PDU session tunnel information between the RAN and the UPF, the control message sent to the UE, the radio resource control information sent to the RAN, etc.
  • N2 The interface between the AMF and the RAN, used to transfer radio bearer control information from the core network side to the RAN.
  • N1 The interface between the AMF and the UE, which has nothing to do with access, and is used to deliver QoS control rules to the UE.
  • N8 The interface between AMF and UDM, which is used for AMF to obtain subscription data and authentication data related to access and mobility management from UDM, and for AMF to register UE current mobility management related information with UDM.
  • N10 The interface between SMF and UDM, which is used for SMF to obtain session management-related subscription data from UDM, and for SMF to register UE current session-related information with UDM.
  • N35 interface between UDM and UDR, used for UDM to obtain user subscription data information from UDR.
  • N36 the interface between PCF and UDR, used for PCF to obtain policy-related subscription data and application data-related information from UDR.
  • N52 The interface between UDM and NEF, which is used for NEF to open network capabilities to third-party application functions.
  • third-party application functions subscribe to UDM through NEF to reachability events of all users in a specific group.
  • NEF also has direct interfaces with AMF and SMF, corresponding to N29 interface and N51 interface respectively (to simplify the illustration, not shown in the above figure), which is used to open the operator's network capabilities to third-party application function entities, the former can be used
  • AMF Access Management Function
  • SMF Session Management Function
  • NEF directly subscribes to the corresponding network events and updates the user configuration information to the AMF, which can be used to update the application configuration data on the SMF/UPF, such as the packet flow description information (packet flow description, PFD) corresponding to the Application ID.
  • PFD packet flow description
  • the above-mentioned network architecture applied to the embodiment of the present application is only an example of a network architecture described from the perspective of a traditional point-to-point architecture and a service-oriented architecture, and the network architecture applicable to the embodiment of the present application is not limited thereto. Any network architecture capable of implementing the functions of the foregoing network elements is applicable to this embodiment of the present application.
  • the name of the interface between network elements in FIG. 2 is just an example, and the name of the interface in a specific implementation may be another name, which is not specifically limited in this application.
  • the name of the message (or signaling) transmitted between the above network elements is only an example, and does not constitute any limitation on the function of the message itself.
  • the foregoing network element may also be called an entity, device, device, or module, which is not specifically limited in this application. Moreover, in this application, for the sake of easy understanding and explanation, the description of the network element is omitted in some descriptions.
  • the SMF network element is referred to as SMF.
  • the "SMF" should be understood as the SMF network element. The following , omitting descriptions for the same or similar situations.
  • the above-mentioned network element or function may be a network element in a hardware device, a software function running on dedicated hardware, or a virtualization function instantiated on a platform (for example, a cloud platform).
  • a platform for example, a cloud platform.
  • the foregoing network element or function may be implemented by one device, or jointly implemented by multiple devices, or may be a functional module in one device, which is not specifically limited in this embodiment of the present application.
  • each component network element is only exemplary, and not all functions of each component network element are required when applied in the embodiment of the present application.
  • each network element such as PCF, AMF, etc.
  • the above-mentioned network elements may also have other names, which are not specifically limited in this embodiment of the present application.
  • some or all of the above-mentioned network elements may use the terms in 5G, or may be named by other names, etc., which will be described in a unified manner here, and will not be described in detail below.
  • each network element of the control plane function in Figure 2 can also communicate through a service interface, for example, the service interface provided by AMF can be Namf; the service interface provided by SMF can be Nsmf; The service interface provided externally can be Nudm, the service interface provided by AF can be Naf; the service interface provided by PCF can be Npcf and so on.
  • AMF can be Namf
  • SMF can be Nsmf
  • the service interface provided externally can be Nudm
  • the service interface provided by AF can be Naf
  • the service interface provided by PCF can be Npcf and so on.
  • FIG. 2 shows a schematic diagram of the architecture based on the service interface.
  • the architecture includes: NSSF, AUSF, UDM, NEF, NRF, PCF, AF, AMF, SMF, UE, RAN, UPF, DN.
  • the service interface provided by NSSF can be Nnssf
  • the service interface provided by NEF can be Nnef
  • the service interface provided by NRF can be Nnrf
  • the service interface provided by AMF can be Namf
  • SMF The service interface provided by UDM can be Nsmf
  • the service interface provided by UDM can be Nudm
  • the service interface provided by AF can be Naf
  • the service interface provided by PCF can be Npcf
  • the service interface provided by AUSF can be Nausf
  • the service interface provided by CHF can be Nchf
  • the interface between the control plane function and RAN and UPF is a non-service interface.
  • the UE is connected to the AMF through the N1 interface, the UE is connected to the RAN through the radio resource control (RRC) protocol; the RAN is connected to the AMF through the N2 interface, and the RAN is connected to the UPF through the N3 interface; the UPF is connected to the DN through the N6 interface, and at the same time , UPF is connected with SMF through N4 interface.
  • RRC radio resource control
  • the RAN is connected to the AMF through the N2 interface
  • the RAN is connected to the UPF through the N3 interface
  • the UPF is connected to the DN through the N6 interface, and at the same time , UPF is connected with SMF through N4 interface.
  • 5G system architecture 5G system architecture
  • a 5G network is taken as an example to briefly describe the process of establishing a PDU session connection and PDU session management for a UE.
  • 5G network provides data exchange service for UE and DN network, which is called PDU connection service.
  • the UE obtains the PDU connection service by initiating a PDU session establishment request to the mobile network.
  • the network side provides the PDU connection service by maintaining the PDU session for the UE.
  • UE In order to realize data exchange between UE and DN network, UE needs to use the PDU connection service provided by the mobile network to establish a DNN-based PDU session (signaling plane process).
  • the establishment of a PDU session includes two basic processes: the UE registers with the mobile network to access the network, and the UE requests the network to establish a PDU session. These two processes belong to the signaling plane interaction process between the UE and the mobile network.
  • the general UE registration and network access process can be simply described as: UE sends a registration request to AMF through (R)AN, and AMF obtains subscription data from a specific UDM according to the user ID. After a series of authentication and authorization operations, the network side finally confirms that the UE is allowed to access the network. At this time, the AMF responds to the UE registration request and sends relevant policy information to the UE, and the UE completes network registration and camping. The AMF on the network side maintains the registration information of the UE and performs mobility management on the UE.
  • the UE After the UE completes registration and access to the network, it can initiate a PDU session establishment request to obtain the PDU connection service of the network.
  • the general PDU session establishment process can be simply described as: UE sends a PDU session establishment request to AMF through RAN, AMF selects SMF to provide session service for UE, saves the corresponding relationship between SMF and PDU session, and sends the session establishment request to SMF, SMF Select the corresponding UPF for the UE to establish a user plane transmission path, and assign an IP address to it.
  • SMF interacts with UPF through N4 interface, and controls UPF to create, modify, and delete corresponding UE N4 sessions (N4 Session/PFCP Session) to realize the control of UPF processing data packets.
  • the SMF issues various data packet processing rules to the UE N4 session in the UPF to complete the control of the UPF processing data packets.
  • the UPF receives the external data packet, it performs packet matching according to the data packet matching rules delivered by the SMF, and forwards the packets according to the forwarding rules.
  • "for indication” may include direct indication and indirect indication, and may also include explicit indication and implicit indication.
  • the information indicated by a certain information (such as the configuration information described below) is called the information to be indicated.
  • the information to be indicated In the specific implementation process, there are many ways to indicate the information to be indicated. For example, but not limited to, it is possible to directly indicate the information to be indicated. Information, such as the information to be indicated or the index of the information to be indicated.
  • the information to be indicated may also be indicated indirectly by indicating other information, where there is an association relationship between the other information and the information to be indicated. It is also possible to indicate only a part of the information to be indicated, while other parts of the information to be indicated are known or agreed in advance.
  • the indication of specific information can also be realized by means of a pre-agreed (for example, protocol-specified) arrangement order of each information, thereby reducing the indication overhead to a certain extent.
  • the "storage" mentioned in the embodiment of the present application may refer to storage in one or more memories.
  • the one or more memories may be provided independently, or may be integrated in an encoder or decoder, a processor, or a communication device.
  • a part of the one or more memories may also be provided separately, and a part may be integrated in a decoder, a processor, or a communication device.
  • the type of storage may be any form of storage medium, which is not limited in this application.
  • the "protocol” involved in the embodiment of the present application may refer to a standard protocol in the communication field, for example, may include LTE protocol, NR protocol and related protocols applied in future communication systems, which is not limited in this application.
  • At least one means one or more, and “multiple” means two or more.
  • And/or describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the contextual objects are an “or” relationship.
  • At least one of the following” or similar expressions refer to any combination of these items, including any combination of single or plural items.
  • At least one (one) of a, b and c may represent: a, or b, or c, or a and b, or a and c, or b and c, or a, b and c, wherein a, b, c can be single or multiple.
  • the UE is used as the terminal device for introduction, but the terminal device of the present application is not limited thereto.
  • Fig. 4 shows a schematic flowchart of an example of a communication method provided by the present application.
  • the access service method 400 is applied to the network architecture shown in FIGS. 1 to 3 above.
  • a terminal central processing unit (central processing unit, CPU)/user sends redundancy configuration to UE1 and UE2.
  • the terminal CPU/user sends redundant configuration to UE1 and UE2.
  • the redundancy configuration may include: redundancy indication, redundancy type, and redundancy identification.
  • the terminal CPU/user may send the redundant configuration to UE1 and UE2 before UE1 and UE2 are respectively inserted into the SIM cards of the subscribers.
  • the redundancy indication is used to indicate to enable redundant transmission of the UE1 and UE2, or the redundancy indication can also be understood as an indication that subsequent network devices need to set the UE1 and UE2 as devices for redundant transmission.
  • the redundancy type may be the type used for redundant transmission and reception, for example, may include the protocol type and related parameters adopted by redundant transmission such as multi-transmission selective reception, active-standby transmission, or multi-link load balancing transmission.
  • the redundancy identifier is unique identifier information of the redundantly paired UE on the network device side. It should be understood that multiple UEs forming the pair have the same redundant identifier.
  • the terminal CPU may refer to an execution module in the wireless terminal that automatically configures a wireless communication module, for example, a wireless communication chip.
  • the user may be an external system that operates and configures the wireless communication terminal, for example, may be a person who operates the terminal device.
  • the terminal CPU/user triggers UE1 and UE2 to register and access the network by powering on the device or by commanding dial-up to access the network. Subsequently, UE1 and UE2 respectively initiate network registration and camp on the wireless network.
  • UE1 and UE2 respectively initiate network registration and camp on the wireless network.
  • 3GPP network access protocols For the sake of simplicity of description, this application will not repeat them here.
  • S403, UE1 and UE2 respectively send the first PDU session request and the second PDU session request to the AMF.
  • UE1 and UE2 respectively initiate a PDU session request to the AMF, wherein the first PDU session request and the second PDU session request carry the same redundant transmission configuration information.
  • the first PDU session request may carry UE1's user subscription identifier, redundancy indication, redundancy type, and redundancy identifier
  • the second PDU session request may carry UE1's user subscription identifier, redundancy indication, redundancy type, and Redundant flags.
  • the AMF determines the same SMF for UE1 and UE2.
  • the AMF After the AMF receives the first PDU session request and the second PDU session request sent by UE1 and UE2, the AMF provides subscription services for UE1 and UE2 according to the redundancy identifier carried in the first PDU session request and the second PDU session request. Subscribers choose the same SMF.
  • the AMF sends the first PDU session request of UE1 and the second PDU session request of UE2 to the SMF.
  • the AMF sends the first PDU session request and the second PDU session request of UE1 and UE2 to the SMF respectively, the first PDU session request of UE1 is used to request to create a packet data unit PDU session for UE1, and the second PDU session request of UE2
  • the session request is used to request to create a packet data unit PDU session for UE2, wherein the first PDU session request can carry UE1's user subscription ID, redundancy indication, redundancy type, and redundancy ID, and the second PDU session request can include UE2 User subscription ID, redundancy indication, redundancy type and redundancy ID.
  • the first SMF determines UPFs for UE1 and UE2.
  • the first SMF determines the same UPF for UE1 and UE2 according to the first PDU session request of UE1 and the second PDU session request of UE2.
  • the SMF may select the same UPF for UE1 and UE2 according to the redundancy identifiers of UE1 and UE2.
  • the process of selecting a UPF reference may be made to the 3GPP related session creation process, which is not limited in this application.
  • the SMF sends a request to create a first PDU session context and a request to create a second PDU session context to the UPF.
  • the SMF determines the UPF for UE1 and UE2, it sends UE1's request for creating the first PDU session context and UE2's request for creating the second PDU session context to the UPF, wherein the request for creating the first PDU session context and the request for creating the second PDU session
  • the session context request carries redundant transport configuration information.
  • the UPF creates a redundancy context.
  • the UPF After the UPF receives the request to create the first PDU session context or the request to create the second PDU session context, the UPF creates a redundant context for the first UE, and obtains a redundant context identifier of the redundant context.
  • the first UE is the first UE received by the UPF to create a PDU session context. It should be understood that when the UPF receives the request for creating a PDU session context from each UE, due to differences in the online time of each specific UE, or The request to create a PDU session context sent by the SMF will be received by the UPF at different times. Therefore, the UPF only needs to create a redundant context for the UE corresponding to the first received request to create a PDU session context, and obtain the redundant context identifier. If the UPF first receives the request to create the first PDU session context, then UE1 is the first UE, or if the UPF first receives the request to create the second PDU session context, then UE2 is the first UE.
  • the redundancy context is used to process UE1 or UE2 redundant messages, such as multi-send and selective-receive scenarios, the redundancy context is responsible for redundant copying of downlink messages and multiple sending of UE1 or UE2 contexts, and uplink redundant The remaining packets are forwarded after redundant deduplication.
  • the redundant context may also be referred to as a redundant transmission context.
  • the UPF creates a PDU session context for UE1 and UE2.
  • the UPF After the UPF has created the redundant context, the UPF creates a PDU session context for UE1 and UE2, obtains the PDU session context identifier, and adds the PDU session context identifier of the UE1 and UE2 to the redundant context.
  • the UPF continues to create the PDU session of the first UE, and when the PDU session of the first UE is successfully created, the UPF obtains the PDU session The session context ID is added to the redundant context.
  • the UPF determines according to the information carried in the request to create a PDU session that UE1, which is paired with the second UE, has already created a PDU session, and the corresponding redundancy context already exists.
  • the UPF directly creates the PDU session context of UE2, obtains the second PDU session context identifier, and associates the PDU session context identifier corresponding to UE2 with the redundancy context.
  • the UPF may create an N4 session context for UE1 and UE2, and obtain the N4 session context identifier.
  • the UPF sends the first response message and the second response message to the SMF.
  • the UPF sends a first response message and a second response message to the SMF, wherein the first response message carries the PDU session identifier of UE1, and the second response message carries PDU session ID of UE2.
  • the communication method 400 provided in this application may also include other steps:
  • the SMF sends session creation response messages to UE1 and UE2 respectively.
  • the SMF sends session creation response messages to UE1 and UE2 respectively.
  • the method 400 may also include a secondary authentication process, which may include:
  • the SMF sends a second authentication request message to the DN-AAA respectively.
  • the SMF decides whether to send the second authentication request message to the DN-AAA according to the local configuration, user subscription identities of UE1 and UE2, and redundancy indication.
  • the secondary authentication request message carries a user identifier, such as a generic public subscription identifier (GPSI), and the user identifier can be used for DN-AAA identification
  • the secondary authentication request message may also carry a redundancy indication, a redundancy type, and a redundancy identifier.
  • the SMF may also decide whether to allow the UE1 subscriber and the UE2 subscriber to form a redundant transmission pair according to the local configuration.
  • DN-AAA confirms according to the local configuration whether the user identities corresponding to UE1 and UE2 allow redundant transmission, whether the user identities corresponding to UE1 and UE2 allow pairing, and initiates UE1/UE2 authentication if pairing is allowed.
  • a secondary authentication failure response is directly sent to the SMF, and at this time, the session establishment between UE1 and UE2 fails.
  • the DN-AAA sends an authentication response message to the SMF.
  • DN-AAA successfully authenticates UE1 and UE2, it records the binding relationship between the redundant identifier and UE1 subscriber and UE2 subscriber, and sends a secondary authentication success response message to SMF to confirm that UE1 and UE2 subscribers can communicate with each other. Twinning enables redundant transmissions.
  • the redundant transmission is bound to the UE equipment, decoupled from the UE subscriber, and the dynamic association of the subscriber pairing for redundant transmission is completed at the stage of creating a PDU session at the UE.
  • the realization of device redundancy sending and receiving has nothing to do with SIM.
  • Fig. 5 shows a schematic flowchart of an example of a communication method provided by the present application.
  • the access service method 500 is applied to the network architecture shown in FIGS. 1 to 3 above.
  • the SMF sends a first request message to the UPF.
  • the first request message is used to request to create a redundant transmission context for UE1 and UE2.
  • the UPF creates a redundancy context.
  • the UPF after receiving the first request message sent by the SMF, the UPF creates redundant contexts for UE1 and UE2.
  • the UPF sends a response message to the first request message to the SMF.
  • the response message of the first request message carries a redundant transmission context identifier.
  • the SMF sends a request to create a first PDU session context and a request to create a second PDU session context to the UPF.
  • the SMF sends UE1's first PDU session context creation request and UE2's second PDU session context creation request to the UPF, where the first PDU session context creation request and the second PDU session context creation request carry redundant transmission configuration Information and redundant transmission context identification.
  • the UPF creates a PDU session context.
  • the UPF when the UPF receives the first PDU session context request and the second PDU session context creation request, the UPF creates a PDU session for UE1 and UE2 respectively, and obtains the context identifier of the PDU session, where the PDU session can be an N4 session .
  • the UPF sends the first response message and the second response message to the SMF.
  • the UPF sends a first response message and a second response message to the SMF, wherein the first response message carries the PDU session identifier of UE1, and the second response message carries PDU session ID of UE2.
  • the SMF sends the first modification request and the second modification request to the UPF.
  • the first modification request message carries the PDU session identifier of UE1
  • the second modification request carries the PDU session identifier of UE2
  • the first modification request is used to indicate that the PDU session identifier of UE1 is added to the redundant transmission context
  • the second modification The request is used to indicate that the PDU session identifier of UE2 is added to the redundant transmission context.
  • the UPF modifies the redundancy context.
  • the UPF adds UE1's PDU session identifier to the redundant transmission context according to the first modification request, and adds UE2's PDU session identifier to the redundant transmission context according to the second modification request. into the redundant transport context.
  • the communication method 500 provided in this application may also include other steps:
  • the indication information is used to indicate that the session identifier of the UE is added to the redundant context, so as to realize the binding of redundant transmission and UE equipment, decoupling from UE subscribers, and creating In the PDU session phase, the dynamic association of contracted users paired for redundant transmission is completed, and the redundant transmission and reception of equipment has nothing to do with SIM.
  • FIG. 6 shows a schematic flow diagram of realizing pairing cancellation of subscribers based on NAS signaling flow.
  • the method 600 includes:
  • UE1 when the SIM card is removed from UE1, UE1 triggers a session deletion process.
  • the SIM card of a subscriber under UE1 may be removed from UE1 and inserted into UE3.
  • the first SMF sends a first delete message to the first UPF.
  • the first SMF sends a first delete message to the first UPF, where the first delete message is used to instruct the first UPF to delete the N4 session context of the UE1.
  • the first SMF sends a second deletion message to the first UPF.
  • the first SMF sends a second deletion message to the first UPF, where the second deletion message is used to instruct the first UPF to delete the redundant transmission context or delete the user subscription identifier of the redundant transmission context UE1.
  • the second deletion message may carry the context identifier of the N4 session of UE1.
  • the second deletion message is used to instruct the first UPF to delete the user subscription identifier of the UE1 in the redundant context.
  • the second deletion message is used to instruct the first UPF to delete the redundancy context.
  • the communication method 600 provided in this application may also include other steps:
  • the first SMF sends indication information to the DN-AAA.
  • the first SMF sends indication information to the DN-AAA, where the indication information is used to instruct UE1 to trigger session deletion.
  • the DN-AAA releases the binding relationship between the redundant identifier and the UE1.
  • the DN-AAAA determines that the UE1 triggers the session deletion
  • the DN-AAA releases the binding relationship between the redundancy identifier and the UE1.
  • the DN-AAA clears records related to the redundant identifier.
  • the first SMF sends a response message to UE1.
  • the first SMF and the first UPF finish deleting the context information of UE1, they send a response message to UE1. It is used to notify UE1 that the session deletion of UE1 has been completed.
  • the UE session redundant transmission is dynamically released during the UE PDU session release phase.
  • Fig. 7 shows a schematic flowchart of an example of a communication method provided by the present application. The following steps are combined to apply the access service method 700 to the network architecture shown in FIGS. 1 to 3 above.
  • the terminal CPU/user acquires equipment identities from UE1 and UE2.
  • the equipment identities may be international mobile equipment identities (international mobile equipment identity, IMEI), and are used to identify each UE in the network.
  • IMEI international mobile equipment identity
  • the terminal CPU/user sends a device pairing request message of UE1 and UE2 to the AF.
  • the device pairing request message carries the device identifiers and redundancy types of UE1 and UE2.
  • the device identities of UE1 and UE2 are used to identify devices, and are not subscriber identity information of UE1 and UE2.
  • the AF saves the redundant pairing and binding relationship between UE1 and UE2, and allocates a redundancy identifier for the paired device, while maintaining the UE1 and UE2 device identifiers and redundancy types associated with the redundancy identifier.
  • the terminal CPU/user acquires network-subscriber identifiers from UE1 and UE2 respectively.
  • the network subscriber identifier may be, for example, a generic public subscription identifier (generic public subscription identifier, GPSI).
  • the terminal CPU/user sends a device binding subscription user request to the AF.
  • the request message carries user identifiers and device identifiers associated with UE1 and UE2.
  • the AF saves the binding relationship between UE1 and UE2 device identifiers and user identifiers
  • the AF sends redundancy configuration request information to the NEF.
  • the redundancy configuration request information includes first indication information or second indication information, where the first indication information is used to instruct the NEF to add the first redundancy configuration information, and the second indication information is used to instruct the NEF to delete the second redundancy configuration information. remaining configuration information.
  • the redundant configuration request message sent by the AF to the NEF includes the first indication information
  • the first The indication information is used to instruct the NEF to add first redundancy configuration information
  • the first redundancy configuration information includes: UE1 and UE2 user identifiers, for example, GPSI, redundancy indication information, redundancy type and redundancy identifier.
  • the AF sends the NEF redundancy configuration request message to include second indication information, and the second indication information uses To instruct NEF to delete the second redundant configuration information, where the second redundant configuration information includes: UE1 and UE2 user identities, which are used to indicate users who delete the configuration, and redundant identities, which are used to indicate UE1 and UE2 users from indicating Redundant transmissions are released in the redundant flag of .
  • the AF may also send the redundancy configuration request message including the first indication information to the NEF.
  • the NEF sends a subscription data modification request to the UDM.
  • the NEF sends a request to modify the subscription data to the UDM.
  • the UDM modifies the subscription data.
  • the UDM modifies the subscription data according to the request.
  • the subscription data modification request is used to instruct the UDM to add the first redundant configuration information of UE1 and UE2.
  • the subscription data modification request is used to instruct the UDM to delete the second redundant configuration information of UE1 and UE2.
  • the UDM sends a subscription data change message to the SMF.
  • the UDM sends a subscription data change message to the SMF, indicating that the subscription data of the UE is changed.
  • the SMF sends a subscription data change message to the UE.
  • the subscription data change message is used to notify UE1 and UE2 to log off the affected session and re-initiate session establishment.
  • the NEF sends a response message to the AF.
  • the response message includes the redundant pair configuration result.
  • the AF subscribes to the NEF for a change notification of the association relationship between the subscriber ID and the device ID.
  • the AF subscribes to the NEF for a change notification of the association relationship between the subscriber ID and the device ID.
  • the NEF sends a change notification to the AF.
  • the NEF sends a change notification to the AF.
  • UE1 and UE2 respectively send PDU session establishment request messages to AMF.
  • UE1 and UE2 respectively initiate a PDU session establishment request message to the AMF.
  • the AMF obtains the subscriber data from the UDM.
  • the subscriber data may include: UE1 and UE2 subscription redundancy indications, redundancy identifiers, redundancy types, and the like.
  • AMF determines SMFs for UE1 and UE2.
  • the AMF selects the same SMF for the UE1 subscriber and the UE2 subscriber according to the acquired redundancy identifier.
  • the AMF sends the first PDU session request of UE1 and the second PDU session request of UE2 to the SMF.
  • the AMF sends the first PDU session request and the second PDU session request of UE1 and UE2 to the SMF respectively, the first PDU session request of UE1 is used to request to create a packet data unit PDU session for UE1, and the second PDU session request of UE2
  • the session request is used to request to create a packet data unit PDU session for UE2, wherein the first PDU session request may carry the user subscription identifier of UE1, and the second PDU session request may carry the user subscription identifier of UE2.
  • the SMF obtains the subscriber data from the UDM.
  • the subscriber data may include: UE1 and UE2 subscription redundancy indications, redundancy identifiers, redundancy types, and the like.
  • the SMF determines UPFs for UE1 and UE2.
  • the SMF selects the same UPF for the UE1 subscriber and the UE2 subscriber according to the acquired redundancy identifier.
  • the SMF sends a request to create a first PDU session context and a request to create a second PDU session context to the UPF.
  • the SMF determines the UPF for UE1 and UE2, it sends UE1's request for creating the first PDU session context and UE2's request for creating the second PDU session context to the UPF, wherein the request for creating the first PDU session context and the request for creating the second PDU session
  • the session context request carries redundant transport configuration information.
  • the UPF creates a redundancy context.
  • the UPF After the UPF receives the request to create the first PDU session context or the request to create the second PDU session context, the UPF creates a redundant context for the first UE, and obtains a redundant context identifier of the redundant context.
  • the first UE is the first UE received by the UPF to create a PDU session context. It should be understood that when the UPF receives the request for creating a PDU session context from each UE, due to differences in the online time of each specific UE, or The request to create a PDU session context sent by the SMF will be received by the UPF at different times. Therefore, the UPF only needs to create a redundant context for the UE corresponding to the first received request to create a PDU session context, and obtain the redundant context identifier. If the UPF first receives the request to create the first PDU session context, then UE1 is the first UE, or if the UPF first receives the request to create the second PDU session context, then UE2 is the first UE.
  • the redundancy context is used to process UE1 or UE2 redundant messages, such as multi-send and selective-receive scenarios, the redundancy context is responsible for redundant copying of downlink messages and multiple sending of UE1 or UE2 contexts, and uplink redundant The remaining packets are forwarded after redundant deduplication.
  • the redundant context may also be referred to as a redundant transmission context.
  • the UPF creates a PDU session context for UE1 and UE2.
  • the UPF After the UPF has created the redundancy context, the UPF creates a PDU session context for UE1 and UE2, obtains the PDU session context identifier, and adds the PDU session context identifier of the UE1 and UE2 to the redundancy context.
  • the UPF continues to create the PDU session of the first UE, and when the PDU session of the first UE is successfully created, the UPF obtains the PDU session The session context ID is added to the redundant context.
  • the UPF determines that UE1, which is paired with the second UE, has already created a PDU session according to the information carried in the request to create a PDU session, and the corresponding redundancy context already exists.
  • the UPF directly creates the PDU session context of UE2, obtains the second PDU session context identifier, and associates the PDU session context identifier corresponding to UE2 with the redundancy context.
  • the UPF may create an N4 session context for UE1 and UE2, and obtain the N4 session context identifier.
  • the UPF sends the first response message and the second response message to the SMF.
  • the UPF sends a first response message and a second response message to the SMF, wherein the first response message carries the PDU session identifier of UE1, and the second response message carries PDU session ID of UE2.
  • the communication method 700 provided in this application may also include other steps:
  • the SMF sends session creation response messages to UE1 and UE2 respectively.
  • the SMF sends session creation response messages to UE1 and UE2 respectively.
  • the redundant transmission is bound to the UE device, decoupled from the UE subscriber, and the dynamic association of the subscriber pair for redundant transmission is completed at the stage of UE creating a PDU session , the implementation of device redundancy sending and receiving has nothing to do with SIM.
  • Fig. 8 shows a schematic flowchart of an example of a communication method provided by the present application.
  • the access service method 800 is applied to the network architecture shown in FIG. 1 to FIG. 3 above.
  • FIG. 8 is based on realizing redundant transmission of equipment in the network capability opening process.
  • step 801 to step 820 can refer to step 701 to step 720 in FIG. 7
  • step 821 to step 828 can refer to corresponding step 507 to step 514 in FIG. .
  • FIG. 9 shows a schematic flow diagram of realizing pairing cancellation of a subscriber based on a network capability opening process.
  • the method 900 includes:
  • UE1 when the SIM card is removed from UE1, UE1 triggers a session deletion process.
  • the SIM card of a subscriber under UE1 may be removed from UE1 and inserted into UE3.
  • the SMF sends a first deletion message to the UPF.
  • the first deletion information is used to indicate to delete the N4 session context of UE1.
  • the SMF sends a second delete message to the UPF.
  • the SMF sends a second deletion message to the UPF, where the second deletion message is used to instruct the UPF to delete the redundant transmission context or delete the user subscription identifier of the redundant transmission context UE1.
  • the second deletion message may carry the context identifier of the N4 session of UE1.
  • the second deletion message is used to instruct the UPF to delete the user subscription identifier of the UE1 in the redundant context.
  • the second deletion message is used to instruct the UPF to delete the redundancy context.
  • the SMF sends a third delete message to the UDM.
  • the SMF invokes the UDM Nudm_UECM_Deregistration interface to delete the session association information.
  • the SMF invokes the UDM Nudm_UECM_Deregistration interface to delete the session association information.
  • the relevant 3GPP process which will not be described in detail in this application.
  • the UDM sends the first change message to the AF through the NEF.
  • the first change message is used to notify the AF that the relationship between the user identifier and the device identifier of UE1 is changed.
  • the first change message may carry indication information, where the indication information is used to instruct the AF to delete the N4 session of UE1.
  • the AF deletes the association relationship between the UE1 device identifier and the user identifier.
  • the AF sends the first indication information to the NEF.
  • the AF calls the NEF interface to send the first indication information to the NEF, where the first indication information is used to instruct the NEF to delete the redundant configuration, and the redundant configuration includes: a user identifier and a redundant identifier.
  • the NEF sends second indication information to the UDM.
  • the NEF invokes the UDM interface to send the second indication information to the UDM
  • the second indication information is used to instruct the UDM to delete the subscription data specified by the user identifier, the configuration related to redundant transmission, for example, delete the redundancy indication, the redundancy type, Redundant identification, etc.
  • the AF sends a second change message to the NEF.
  • the AF sends a second change message to the NEF, where the second change message is used to instruct the NEF to unsubscribe from the UE1 user ID and change the association relationship between the device ID, and the second change message may carry user ID information.
  • step numbers of the various flow charts described in the embodiment are only an example of the execution flow, and do not constitute a restriction on the sequence of execution of the steps. There is no strict order of execution.
  • steps that must be executed are steps that must be executed, and some steps may be added or deleted on the basis of each flow chart according to actual needs.
  • FIG. 4 to FIG. 9 the method for implementing the communication provided by the present application is described in detail.
  • FIG. 10 and FIG. 11 the communication device provided in the embodiment of the present application is described in detail.
  • FIG. 10 is a schematic structural diagram of a possible communication device provided by an embodiment of the present application.
  • a communication device 1000 includes a processing unit 1010 and a transceiver unit 1020 .
  • the communication device 1000 is used to implement the function or operation module of the SMF in the method embodiment shown in FIGS. function or operation module, or the communication device 1000 is used to implement the AF function or operation module in the method embodiment shown in Figure 7 to Figure 9 above, or the communication device 1000 is used to implement the above Figure 7 to Figure 9
  • the function or operation module of the NEF in the illustrated method embodiment, the module may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • the transceiver unit 1020 is used to receive the first PDU session request from the first terminal device and the second PDU session request from the second terminal device , wherein the first PDU session request and the second PDU session request carry the same redundant transmission configuration information; send a request to create the first PDU session context and a request to create the second PDU session context to the user plane functional entity UPF, and create the first PDU
  • the session context request and the creation of the second PDU session context request carry redundant transmission configuration information; and receive the first response message and the second response message from the UPF, the first response message carries the PDU session identifier of the first terminal device, and the second response The message carries the PDU session identifier of the second terminal device.
  • the transceiver unit 1020 is used to receive the first PDU session request from the first terminal device and the second PDU session request from the second terminal device , wherein the first PDU session request and the second PDU session request carry the same redundant transmission configuration information; send a request to create the first PDU session context and a request to create the second PDU session context to the user plane functional entity UPF, and create the first PDU
  • the session context request and the creation of the second PDU session context request carry redundant transmission configuration information; and receive the first response message and the second response message from the UPF, the first response message carries the PDU session identifier of the first terminal device, and the second response The message carries the PDU session identifier of the second terminal device.
  • the transceiver unit 1020 is used to send a first deletion message and a second deletion message to the UPF, wherein the first deletion message is used to indicate deletion of N4 The context, the second deletion message is used to indicate to delete the user subscription identifier in the redundant transmission context and/or to delete the redundant transmission context.
  • the processing unit 1010 is used to obtain the first redundant transmission configuration information of the first terminal device from the unified data management UDM according to the first PDU session request , and acquiring second redundant transmission configuration information of the second terminal device from the UDM according to the second PDU session request.
  • the transceiver unit 1020 is configured to receive a first PDU session request from a first terminal device and a second PDU session request from a second terminal device, and send a request for creating a first PDU session context and a request for creating a second PDU session to the user plane functional entity UPF A context request, wherein the request to create the first PDU session context carries the first redundant transmission configuration information, the request to create the second PDU session context carries the second redundant transmission configuration information, and receives the first response message and the second response from the UPF message, the first response message carries the PDU session identifier of the first terminal device, and the second response message carries the PDU session identifier of the second terminal device.
  • the processing unit 1010 is used to obtain the first redundant transmission configuration information of the first terminal device from the unified data management UDM according to the first PDU session request , and acquiring second redundant transmission configuration information of the second terminal device from the UDM according to the second PDU session request.
  • the transceiver unit 1020 is configured to receive a first PDU session request from a first terminal device and a second PDU session request from a second terminal device, and send a request for creating a first PDU session context and a request for creating a second PDU session to the user plane functional entity UPF A context request, wherein the request to create the first PDU session context carries the first redundant transmission configuration information, the request to create the second PDU session context carries the second redundant transmission configuration information, and receives the first response message and the second response from the UPF message, the first response message carries the PDU session identifier of the first terminal device, and the second response message carries the PDU session identifier of the second terminal device.
  • the transceiver unit 1020 is used to send the first deletion message and the second deletion message to the UPF.
  • the first deletion message is used to indicate the deletion of the PDU context
  • the second deletion message is used to indicate the deletion of the user subscription identifier in the redundant transmission context and/or the deletion of the redundant transmission context.
  • the processing unit 1010 is used to determine the same session management function network element for the first terminal device and the second terminal device according to the redundant transmission configuration information.
  • SMF The transceiver unit 1020 is configured to receive a first PDU session request from a first terminal device and a second PDU session request from a second terminal device, wherein the first PDU session request and the second PDU session request carry the same
  • the configuration information is transmitted redundantly, and the first PDU session request and the second PDU session request are sent to the SMF.
  • the processing unit 1010 is used to determine the same session management function network element for the first terminal device and the second terminal device according to the redundant transmission configuration information SMF.
  • the transceiver unit 1020 is configured to receive a first PDU session request from a first terminal device and a second PDU session request from a second terminal device, wherein the first PDU session request and the second PDU session request carry the same
  • the configuration information is transmitted redundantly, and the first PDU session request and the second PDU session request are sent to the SMF.
  • the processing unit 1010 is used to determine the same session management function network element for the first terminal device and the second terminal device according to the redundant transmission configuration information SMF.
  • the transceiver unit 1020 is configured to receive the first PDU session request from the first terminal device and the second PDU session request from the second terminal device, and send the first PDU session request and the second PDU session request to the SMF.
  • the processing unit 1010 is used to determine the same session management function network element for the first terminal device and the second terminal device according to the redundant transmission configuration information. SMF.
  • the transceiver unit 1020 is configured to receive the first PDU session request from the first terminal device and the second PDU session request from the second terminal device, and send the first PDU session request and the second PDU session request to the SMF.
  • the processing unit 1010 is used to obtain the first configuration information; the transceiver unit 1020 sends a redundant configuration request message to the NEF based on the first configuration information, and the redundant The remaining configuration request message includes first indication information or second indication information, where the first indication information is used to instruct the NEF to add the first redundant configuration information, and the second indication information is used to instruct the NEF to delete the second redundant configuration information.
  • the processing unit 1010 is used to obtain the first configuration information; the transceiver unit 1020 sends a redundant configuration request message to the NEF based on the first configuration information, and the redundant configuration
  • the remaining configuration request message includes first indication information or second indication information, where the first indication information is used to instruct the NEF to add the first redundant configuration information, and the second indication information is used to instruct the NEF to delete the second redundant configuration information.
  • the processing unit 1010 is used to send a request to modify the subscription data to the UDM according to the redundant configuration request message; the transceiver unit 1020 is used to receive the request from the application function entity A redundant configuration request message of the AF, where the redundant configuration request message includes first indication information or second indication information, wherein the first indication information is used to indicate the first redundant configuration information for adding at least two terminal devices, and the second The indication information is used to indicate to delete the second redundant configuration information.
  • processing unit 1010 and the transceiver unit 1020 can be directly obtained by referring to the relevant descriptions in the method embodiments shown in FIG. 4 to FIG. 9 , and details are not repeated here.
  • FIG. 11 is a schematic structural diagram of another possible communication device provided by an embodiment of the present application.
  • a communication device 1100 includes a processor 1110 and an interface circuit 1120 .
  • the processor 1110 and the interface circuit 1120 are coupled to each other.
  • the interface circuit 1120 may be a transceiver or an input-output interface.
  • the communication device 1100 may further include a memory 1130 for storing instructions executed by the processor 1110 or storing input data required by the processor 1110 to execute the instructions or storing data generated by the processor 1110 after executing the instructions.
  • the processor 1110 is used to implement the functions of the processing unit 1010 described above
  • the interface circuit 1120 is used to implement the functions of the transceiver unit 1020 described above.
  • the processor in the embodiments of the present application can be a central processing unit (Central Processing Unit, CPU), and can also be other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application-specific integrated circuits (Application Specific Integrated Circuit, ASIC), Field Programmable Gate Array (Field Programmable Gate Array, FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.
  • a general-purpose processor can be a microprocessor, or any conventional processor.
  • the processor can be random access memory (Random Access Memory, RAM), flash memory, read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable In addition to programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM), registers, hard disk, mobile hard disk, CD-ROM or any other form of storage medium known in the art middle.
  • An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium.
  • the storage medium may also be a component of the processor.
  • the processor and storage medium can be located in the ASIC.
  • the ASIC can be located in a network device or a terminal device. Certainly, the processor and the storage medium may also exist in the network device or the terminal device as discrete components.
  • all or part of them may be implemented by software, hardware, firmware or any combination thereof.
  • software When implemented using software, it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product comprises one or more computer programs or instructions.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a terminal device, or other programmable devices.
  • the computer program or instructions may be stored in or transmitted via a computer-readable storage medium.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server integrating one or more available media.
  • the available medium may be a magnetic medium, such as a floppy disk, a hard disk, or a magnetic tape; it may also be an optical medium, such as a DVD; it may also be a semiconductor medium, such as a solid state disk (solid state disk, SSD).

Landscapes

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

Abstract

本申请实施例提供了一种通信方法和装置，该方法包括：SMF接收来自第一终端设备的第一PDU会话请求，和第二终端设备的第二PDU会话请求，其中，该第一PDU会话请求和该第二PDU会话请求携带相同的冗余传输配置信息；该SMF向UPF发送创建第一PDU会话上下文请求和创建第二PDU会话上下文请求，该创建第一PDU会话上下文请求和该创建第二PDU会话上下文请求携带该冗余传输配置信息；SMF接收来自UPF的第一响应消息和第二响应消息，该第一响应消息携带该第一终端设备的PDU会话标识，该第二响应消息携带该第二终端设备的PDU会话标识。基于该方法和装置，能够在终端设备与签约用户解耦情况下，实现设备冗余传输。

Description

一种通信的方法和装置
本申请要求于2021年11月05日提交中国国家知识产权局、申请号202111307021.4、申请名称为“一种通信的方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信领域，并且，更具体地，涉及一种通信的方法和装置。
背景技术
当前，多用户设备(user equipment，UE)在冗余传输是通过用户签约完成的，即发放到用户手中的用户识别模块(subscriber identity module，SIM)其签约的冗余传输关系是相对固定的。用户在使用SIM卡的过程中必须牢记两张SIM卡之间的冗余签约关系，不允许与其他SIM混用。因此，为了保证冗余传输的可靠性，每个用户会同时存在非冗余传输SIM卡和冗余传输SIM卡，通过静态签约冗余传输。然而在存在许多签约用户的场景下时，常常容易出现SIM用错问题。
因此，为了避免静态签约冗余传输下造成的SIM卡的混用，如何在用户设备盲插SIM卡的情况下，实现用户设备签约用户之间的冗余传输结对，是亟待解决的问题。
发明内容
本申请实施例提供一种通信的方法和装置，能够在终端设备与签约用户解耦情况下，实现设备冗余传输。
第一方面，提供了一种通信方法，所述方法应用于SMF，或者，也可以由配置于SMF中的芯片或电路执行，本申请对此不作限定。该方法包括：会话管理功能网元SMF接收来自第一终端设备的第一PDU会话请求，和第二终端设备的第二PDU会话请求，其中，所述第一PDU会话请求和所述第二PDU会话请求携带相同的冗余传输配置信息；所述SMF向用户面功能实体UPF发送创建第一PDU会话上下文请求和创建第二PDU会话上下文请求，所述创建第一PDU会话上下文请求和所述创建第二PDU会话上下文请求携带所述冗余传输配置信息；所述SMF接收来自所述UPF的第一响应消息和第二响应消息，所述第一响应消息携带所述第一终端设备的PDU会话标识，所述第二响应消息携带所述第二终端设备的PDU会话标识。
基于上述方案，SMF通过终端设备的PDU会话请求获取冗余传输配置信息，通过在创建多个终端设备的PDU会话流程中将冗余传输配置信息发送给相同的UPF，可以在终端设备与签约用户解耦情况下，实现设备冗余传输，且不必发起单独的冗余传输会话过程，能够节约资源。
结合第一方面，在第一方面的某些实现方式中，在所述SMF向用户面功能实体UPF 发送创建第一PDU会话上下文请求和创建第二PDU会话上下文请求之前，所述方法还包括：所述SMF向所述UPF发送第一请求消息，所述第一请求消息用于请求为所述第一终端设备和所述第二终端设备创建冗余传输上下文；所述SMF接收来自所述UPF的所述第一请求的响应消息，所述第一请求的响应消息包括冗余传输上下文标识，其中，所述创建第一PDU会话上下文请求和所述创建第二PDU会话上下文请求还携带所述冗余传输上下文标识。
基于上述方案，SMF向UPF发送第一请求用于创建冗余上下文，通过UPF为冗余传输的终端设备创建相同的冗余上下文，以达到实现冗余传输的目的。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：所述SMF根据所述冗余配置信息为所述第一终端设备和所述第二终端设备确定所述UPF。
应理解，该SMF为第一终端设备和第二终端设备确定的UPF是相同的。
结合第一方面，在第一方面的某些实现方式中，所述SMF向所述UPF发送所述第一终端设备的第一修改请求和所述第二终端设备的第二修改请求，所述第一修改请求消息携带所述第一终端设备的PDU会话标识，所述第二修改请求携带所述第二终端设备的PDU会话标识，所述第一修改请求用于指示将所述第一终端设备的PDU会话标识添加到所述冗余传输上下文中，所述第二修改请求用于指示将所述第二终端设备的PDU会话标识添加到所述冗余传输上下文中。
基于上述方案，通过将终端设备PDU会话标识添加到冗余传输上下文中，实现冗余传输与终端设备的绑定。
结合第一方面，在第一方面的某些实现方式中，所述冗余传输配置信息包括：冗余指示信息、冗余类型以及冗余标识，所述冗余指示信息用于指示开启冗余传输。
结合第一方面，在第一方面的某些实现方式中，所述冗余类型以及所述冗余标识是通过用户设置的。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：
所述SMF向所述UPF发送第一删除消息和第二删除消息，所述第一删除消息用于指示删除PUD会话上下文，所述第二删除消息用于指示删除所述冗余传输上下文中的用户签约标识和/或删除所述冗余传输上下文。
基于上述方案，当冗余传输结束后，通过删除信息删除PDU会话上下文或者删除冗余传输上下文中某一个终端设备的用户签约标识或者冗余传输上下文，能够节约系统的资源。
第二方面，提供了一种通信方法，所述方法应用于SMF，或者，也可以由配置于SMF中的芯片或电路执行，本申请对此不作限定。该方法包括：会话管理功能网元SMF接收来自第一终端设备的第一PDU会话请求，和第二终端设备的第二PDU会话请求；所述SMF根据所述第一PDU会话请求向统一数据管理UDM获取所述第一终端设备的第一冗余传输配置信息，以及，所述SMF根据所述第二PDU会话请求向所述UDM获取所述第二终端设备的第二冗余传输配置信息；所述SMF向用户面功能实体UPF发送创建第一PDU会话上下文请求和创建第二PDU会话上下文请求，所述创建第一PDU会话上下文请求携带所述第一冗余传输配置信息，所述创建第二PDU会话上下文请求携带所述第二冗余传输配置信息；所述SMF接收来自所述UPF的第一响应消息和第二响应消息，所述 第一响应消息携带所述第一终端设备的PDU会话标识，所述第二响应消息携带所述第二终端设备的PDU会话标识。
基于上述方案，SMF通过向UDM获取终端设备的冗余传输配置信息，并通过创建PDU会话流程将冗余传输配置信息发送给UPF，节约了资源，实现了冗余传输终端设备与用户签约信息的解耦。
结合第二方面，在第二方面的某些实现方式中，在所述SMF向用户面功能实体UPF发送创建第一PDU会话上下文请求和创建第二PDU会话上下文请求之前，所述方法还包括：所述SMF向所述UPF发送第一请求消息，所述第一请求消息用于请求为所述第一终端设备和所述第二终端设备创建冗余传输上下文；所述SMF接收来自所述UPF的所述第一请求的响应消息，所述第一请求的响应消息包括冗余传输上下文标识，其中，所述创建第一PDU会话上下文请求和所述创建第二PDU会话上下文请求还携带所述冗余传输上下文标识。
结合第二方面，在第二方面的某些实现方式中，所述SMF向所述UPF发送所述第一终端设备的第一修改请求和所述第二终端设备的第二修改请求，所述第一修改请求消息携带所述第一终端设备的PDU会话标识，所述第二修改请求携带所述第二终端设备的PDU会话标识，所述第一修改请求用于指示将所述第一终端设备的PDU会话标识添加到所述冗余传输上下文中，所述第二修改请求用于指示将所述第二终端设备的PDU会话标识添加到所述冗余传输上下文中。
结合第二方面，在第二方面的某些实现方式中，所述第一冗余传输配置信息包括：冗余类型、冗余标识以及所述第一终端的签约冗余指示信息，所述第二冗余传输配置信息包括：所述冗余类型、所述冗余标识以及所述第二终端的签约冗余指示信息。
结合第二方面，在第二方面的某些实现方式中，所述冗余类型以及所述冗余标识是通过应用功能网元AF设置的。
结合第二方面，在第二方面的某些实现方式中，所述方法还包括：所述SMF向所述UPF发送第一删除消息和第二删除消息，所述第一删除消息用于指示删除PUD会话上下文，所述第二删除消息用于指示删除所述冗余传输上下文中的用户签约标识和/或删除所述冗余传输上下文。
第三方面，提供了一种通信方法，所述方法应用于AMF，或者，也可以由配置于AMF中的芯片或电路执行，本申请对此不作限定。该方法包括：接入与移动性管理功能网元AMF接收来自第一终端设备的第一PDU会话请求，和第二终端设备的第二PDU会话请求，其中，所述第一PDU会话请求和所述第二PDU会话请求携带相同的冗余传输配置信息；所述AMF根据所述冗余传输配置信息为所述第一终端设备和所述第二终端设备确定相同的会话管理功能网元SMF；所述AMF向所述SMF发送所述第一PDU会话请求和所述第二PDU会话请求。
基于上述方案，AMF通过终端设备发送的冗余传输配置信息为不同的终端设备选择相同的SMF来实现冗余传输，提升了系统的性能。
结合第三方面，在第三方面的某些实现方式中，所述冗余传输配置信息包括：冗余指示信息、冗余类型以及冗余标识，所述冗余指示信息用于指示开启冗余传输，其中，所述AMF根据所述冗余传输配置信息为所述第一终端设备和所述第二终端设备确定相同的 SMF，包括：所述AMF根据所述冗余标识为所述第一终端设备和所述第二终端设备确定相同的SMF。
第四方面，提供了一种通信方法，所述方法应用于AMF，或者，也可以由配置于AMF中的芯片或电路执行，本申请对此不作限定。该方法包括：接入与移动性管理功能网元AMF接收来自第一终端设备的第一PDU会话请求，和第二终端设备的第二PDU会话请求；所述AMF根据所述第一PDU会话请求向统一数据管理UDM获取所述第一终端设备的第一冗余传输配置信息，以及，所述AMF根据所述第二PDU会话请求向所述UDM获取所述第二终端设备的第二冗余传输配置信息；所述AMF根据所述第一冗余传输配置信息和所述第二冗余传输配置信息为所述第一终端设备和所述第二终端设备确定相同的会话管理功能网元SMF；所述AMF向所述SMF发送所述第一PDU会话请求和所述第二PDU会话请求。
基于上述方案，AMF通过向UDM获取终端设备冗余传输配置信息来为不同的终端设备选择相同的SMF来实现冗余传输，提升了系统的性能。
结合第四方面，在第四方面的某些实现方式中，所述第一冗余传输配置信息包括：冗余类型、冗余标识以及所述第一终端的签约冗余指示信息、所述第二冗余传输配置信息包括：所述冗余类型、所述冗余标识以及所述第二终端的签约冗余指示信息，其中，所述AMF根据所述第一冗余传输配置信息和所述第二冗余传输配置信息为所述第一终端设备和所述第二终端设备确定相同的SMF，包括：所述AMF根据所述冗余标识为所述第一终端设备和所述第二终端设备确定相同的SMF。
第五方面，提供了一种通信方法，所述方法应用于AF，或者，也可以由配置于AF中的芯片或电路执行，本申请对此不作限定。该方法包括：应用功能实体AF获取第一配置信息；所述AF基于所述第一配置信息向网络开放功能实体NEF发送冗余配置请求消息，所述冗余配置请求消息包括第一指示信息或第二指示信息，所述第一指示信息用于指示所述NEF添加第一冗余配置信息，所述第二指示信息用于指示所述NEF删除第二冗余配置信息。
结合第五方面，在第五方面的某些实现方式中，所述AF基于所述第一配置信息向网络开放功能实体NEF发送冗余配置请求消息，包括：所述AF确定第一终端设备和所述第一终端设备的签约用户为首次绑定，以及第二终端设备与和所述第二终端设备的签约用户为首次绑定；所述AF向所述NEF发送冗余配置请求消息，所述冗余配置请求消息包括第一指示信息，所述第一冗余配置信息包括：所述第一终端设备的用户签约标识、所述第二终端的用户签约标识、冗余指示信息、冗余类型以及冗余标识，所述冗余指示信息用于指示开启冗余传输。
结合第五方面，在第五方面的某些实现方式中，所述AF基于所述第一配置信息向网络开放功能实体NEF发送冗余配置请求消息，包括：所述AF确定第一终端设备和所述第一终端设备的签约用户不是首次绑定，以及第二终端设备与和所述第二终端设备的签约用户不是首次绑定；所述AF向所述NEF发送冗余配置请求消息，包括第二指示信息，所述第二冗余配置信息包括：所述第一终端设备的用户签约标识、所述第二终端设备的用户签约标识、以及冗余标识。
结合第五方面，在第五方面的某些实现方式中，所述第一配置信息包括冗余类型、所 述第一终端设备的设备标识、所述第一终端设备的签约用户标识、所述第二终端设备的设备标识、所述第二终端设备的签约用户标识。
第六方面，提供了一种通信方法，所述方法应用于NEF，或者，也可以由配置于NEF中的芯片或电路执行，本申请对此不作限定。该方法包括：网络开放功能实体NEF接收来自应用功能实体AF的冗余配置请求消息，所述冗余配置请求消息包括第一指示信息或第二指示信息，其中，所述第一指示信息用于指示添加至少两个终端设备的第一冗余配置信息，所述第二指示信息用于指示删除第二冗余配置信息；所述NEF根据所述冗余配置请求消息向统一数据管理UDM发送修改签约数据请求。
结合第六方面，在第六方面的某些实现方式中，第一终端设备和所述第一终端设备的签约用户为首次绑定，以及第二终端设备与和所述第二终端设备的签约用户为首次绑定时，所述冗余配置请求消息包括第一指示信息，所述NEF根据所述冗余配置请求消息向统一数据管理UDM发送修改签约数据请求，包括：所述NEF根据所述第一指示信息向所述UDM发送修改签约数据请求，所述修改签约数据请求用于指示所述UDM添加第一冗余配置信息。
结合第六方面，在第六方面的某些实现方式中，所述第一冗余配置信息包括：所述第一终端设备的用户签约标识、所述第二终端的用户签约标识、冗余指示信息、冗余类型以及冗余标识，所述冗余指示信息用于指示开启冗余传输。
结合第六方面，在第六方面的某些实现方式中，当第一终端设备和所述第一终端设备的签约用户不是首次绑定，以及第二终端设备与和所述第二终端设备的签约用户不是首次绑定时，所述冗余配置请求消息包括第二指示信息，所述NEF根据所述冗余配置请求消息向统一数据管理UDM发送修改签约数据请求，包括：所述NEF根据所述第二指示信息向所述UDM发送修改签约数据请求，所述修改签约数据请求用于指示所述UDM删除第二冗余配置信息。
结合第六方面，在第六方面的某些实现方式中，所述第二冗余配置信息包括：所述第一终端设备的用户签约标识、所述第二终端设备的用户签约标识、以及冗余标识。
第七方面，提供了一种通信方法，所述方法应用于UPF，或者，也可以由配置于UPF中的芯片或电路执行，本申请对此不作限定。该方法包括：用户面功能实体UPF接收来自会话管理功能网元SMF的创建第一PDU会话上下文请求和创建第二PDU会话上下文请求，所述创建第一PDU会话上下文请求和所述创建第二PDU会话上下文请求携带冗余传输配置信息；所述UPF根据所述冗余传输配置信息创建冗余传输上下文；所述UPF向所述SMF发送第一响应消息和第二响应消息，所述第一响应消息携带所述第一终端设备的PDU会话标识，所述第二响应消息携带所述第二终端设备的PDU会话标识。
结合第七方面，在第七方面的某些实现方式中，所述方法还包括：所述UPF根据所述第一PDU会话上下文请求为第一终端设备创建第一PDU会话上下文，以及根据所述第二PDU会话上下文请求为第二终端设备创建第二PDU会话上下文。
结合第七方面，在第七方面的某些实现方式中，所述方法还包括：所述UPF将所述第一终端设备的PDU会话标识添加到所述冗余传输上下文中，所述UPF将所述第二终端设备的PDU会话标识添加到所述冗余传输上下文中。
第八方面，提供了一种通信方法，所述方法应用于UPF，或者，也可以由配置于UPF 中的芯片或电路执行，本申请对此不作限定。该方法包括：用户面功能实体UPF接收来自会话管理功能网元SMF的第一请求消息，所述第一请求消息用于请求为所述第一终端设备和所述第二终端设备创建冗余传输上下文；所述UPF根据所述冗余传输配置信息创建冗余传输上下文；所述UPF向所述SMF发送第一请求的响应消息，所述第一请求的响应消息包括冗余传输上下文标识。
结合第八方面，在第八方面的某些实现方式中，所述方法还包括：所述UPF接收来自会话管理功能网元SMF的创建第一PDU会话上下文请求和创建第二PDU会话上下文请求；所述UPF向所述SMF发送第一响应消息和第二响应消息，所述第一响应消息携带所述第一终端设备的PDU会话标识，所述第二响应消息携带所述第二终端设备的PDU会话标识。
结合第八方面，在第八方面的某些实现方式中，所述方法还包括：所述UPF根据所述第一PDU会话上下文请求为第一终端设备创建第一PDU会话上下文，以及根据所述第二PDU会话上下文请求为第二终端设备创建第二PDU会话上下文。
结合第八方面，在第八方面的某些实现方式中，所述方法还包括：所述UPF接收来自所述SMF的第一修改请求和所述第二终端设备的第二修改请求，所述第一修改请求消息携带所述第一终端设备的PDU会话标识，所述第二修改请求携带所述第二终端设备的PDU会话标识；所述UPF根据所述第一修改请求将所述第一终端设备的PDU会话标识添加到所述冗余传输上下文中，所述UPF根据所述第二修改请求将所述第二终端设备的PDU会话标识添加到所述冗余传输上下文中。
第九方面，提供了一种通信装置，包括用于实现前述第一方面或第二方面的任意可能的实现方式中的方法的功能模块。
第十方面，提供了一种通信装置，包括用于实现前述第三方面或第四方面的任意可能的实现方式中的方法的功能模块。
第十一方面，提供了一种通信装置，包括用于实现前述第五方面的任意可能的实现方式中的方法的功能模块。
第十二方面，提供了一种通信装置，包括用于实现前述第六方面的任意可能的实现方式中的方法的功能模块。
第十三方面，提供了一种通信装置，包括用于实现前述第七方面或第八方面的任意可能的实现方式中的方法的功能模块。
第十四方面，提供了一种通信装置，包括处理器和接口电路，接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至该处理器或将来自该处理器的信号发送给该通信装置之外的其它通信装置，该处理器通过逻辑电路或执行代码指令用于实现前述第一方面或第二方面的任意可能的实现方式中的方法。
第十五方面，提供了一种通信装置，包括处理器和接口电路，该接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至该处理器或将来自该处理器的信号发送给该通信装置之外的其它通信装置，该处理器通过逻辑电路或执行代码指令用于实现前述第三方面或第四方面的任意可能的实现方式中的方法。
第十六方面，提供了一种通信装置，包括处理器和接口电路，该接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至该处理器或将来自该处理器的信号发 送给该通信装置之外的其它通信装置，该处理器通过逻辑电路或执行代码指令用于实现前述第五方面的任意可能的实现方式中的方法。
第十七方面，提供了一种通信装置，包括处理器和接口电路，该接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至该处理器或将来自该处理器的信号发送给该通信装置之外的其它通信装置，该处理器通过逻辑电路或执行代码指令用于实现前述第六方面的任意可能的实现方式中的方法。
第十八方面，提供了一种通信装置，包括处理器和接口电路，该接口电路用于接收来自该通信装置之外的其它通信装置的信号并传输至该处理器或将来自该处理器的信号发送给该通信装置之外的其它通信装置，该处理器通过逻辑电路或执行代码指令用于实现前述第七方面或第八方面的任意可能的实现方式中的方法。
第十九方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序或指令，当该计算机程序或指令被执行时，实现前述第一方面或第二方面的任意可能的实现方式中的方法。
第二十方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序或指令，当该计算机程序或指令被执行时，实现前述第三方面或第四方面的任意可能的实现方式中的方法。
第二十一方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序或指令，当该计算机程序或指令被执行时，实现前述第五方面的任意可能的实现方式中的方法。
第二十二方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序或指令，当该计算机程序或指令被执行时，实现前述第六方面的任意可能的实现方式中的方法。
第二十三方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序或指令，当该计算机程序或指令被执行时，实现前述第七方面或第八方面的任意可能的实现方式中的方法。
第二十四方面，提供了一种包含指令的计算机程序产品，当该指令被运行时，实现前述第一方面或第二方面的任意可能的实现方式中的方法。
第二十五方面，提供了一种包含指令的计算机程序产品，当该指令被运行时，实现前述第三方面或第四方面的任意可能的实现方式中的方法。
第二十六方面，提供了一种包含指令的计算机程序产品，当该指令被运行时，实现前述第五方面的任意可能的实现方式中的方法。
第二十七方面，提供了一种包含指令的计算机程序产品，当该指令被运行时，实现前述第六方面的任意可能的实现方式中的方法。
第二十八方面，提供了一种包含指令的计算机程序产品，当该指令被运行时，实现前述第七方面或第八方面的任意可能的实现方式中的方法。
第二十九方面，提供了一种计算机程序，该计算机程序包括代码或指令，当该代码或指令被运行时，实现前述第一方面或第二方面的任意可能的实现方式中的方法。
第三十方面，提供了一种计算机程序，该计算机程序包括代码或指令，当该代码或指令被运行时，实现前述第三方面或第四方面的任意可能的实现方式中的方法。
第三十一方面，提供了一种计算机程序，该计算机程序包括代码或指令，当该代码或指令被运行时，实现前述第五方面的任意可能的实现方式中的方法。
第三十二方面，提供了一种计算机程序，该计算机程序包括代码或指令，当该代码或指令被运行时，实现前述第六方面的任意可能的实现方式中的方法。
第三十三方面，提供了一种计算机程序，该计算机程序包括代码或指令，当该代码或指令被运行时，实现前述第七方面或第八方面的任意可能的实现方式中的方法。
第三十四方面，提供一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现前述第一方面或第二方面的任意可能的实现方式中的方法。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第三十五方面，提供一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现前述第三方面或第四方面的任意可能的实现方式中的方法。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第三十六方面，提供一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现前述第五方面的任意可能的实现方式中的方法。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第三十七方面，提供一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现前述第六方面的任意可能的实现方式中的方法。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第三十八方面，提供一种芯片系统，该芯片系统包括处理器，还可以包括存储器，用于实现前述第一方面至第八方面的任意可能的实现方式中的方法。该芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。
第三十九方面，提供一种通信系统，该通信系统包括第九方面至第十八方面中任意可能的所述的装置。
附图说明
图1示出了适用于本申请实施例的通信系统100的示意图。
图2示出了一个基本的5G系统200的架构示意图。
图3示出了基于服务化接口的架构示意图。
图4示出了本申请实施例提供的一种通信方法400的流程示意图。
图5示出了本申请实施例提供的一种通信方法500的流程示意图。
图6示出了本申请实施例提供的一种通信方法600的流程示意图。
图7示出了本申请实施例提供的一种通信方法700的流程示意图。
图8示出了本申请实施例提供的一种通信方法800的流程示意图。
图9示出了本申请实施例提供的一种通信方法900的流程示意图。
图10为本申请实施例提供的通信装置1000的示意性框图。
图11为本申请实施例提供的另一种通信装置1100的示意性框图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
图1是适用于本申请实施例的通信系统100的示意图。
如图1所示，该通信系统100可以包括至少一个核心网(core network，CN)网元1200，包括一个或多个接入网设备，比如接入网设备1101、接入网设备1102，以及至少一个终端设备1301和/或终端设备1302。其中，终端设备可接入到无线网络，以通过无线网络获取外网(例如数据网络(data network，DN)的服务，或者通过无线网络与其它设备通信，如可以与其它终端设备通信。无线网络包括RAN和CN，RAN或AN，用于将终端设备接入到无线网络，CN用于对终端设备进行管理并提供与DN通信的网关。
图2示出了一个基本的5G系统200的架构示意图。如图2所示，系统200包括：PCF、AMF、会话管理功能(session management function，SMF)、无线接入网(radio access network，RAN)、统一数据管理(unified data management，UDM)、数据网络(data network，DN)、用户面功能(user plane function，UPF)、UE、应用功能(application function，AF)、和/或统一数据存储(unified data repository，UDR)。可选地，图2中还可以包括以下功能(图2中未示出)：网络切片选择功能(network slice selection function，NSSF)、认证服务器功能(authentication server function，AUSF)、能力开放功能(network exposure function，NEF)、或网络存储功能(NF repository function，NRF)。
其中，各网元主要功能描述如下：
1、终端设备
本申请实施例中的终端设备，可以是：用户设备(user equipment，UE)、移动台(mobile station，MS)、移动终端(mobile terminal，MT)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。
终端设备可以是一种向用户提供语音/数据连通性的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些终端的举例为：移动手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self-driving or autopilot)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备，未来5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功 能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。此外，在本申请实施例中，终端设备还可以是物联网(internet of things，IoT)系统中的终端设备。
2、无线接入网
无线接入网是基于无线通信技术实现接入网络功能的接入网。无线接入网能够管理无线资源，为终端提供无线接入或者空口接入服务，进而完成控制信号和用户数据在终端和核心网之间的转发。
作为示例而非限定，无线接入网可以是LTE系统中的演进型基站(evolved NodeB，eNB或eNodeB)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该接入设备可以为中继站、接入点、车载设备、可穿戴设备以及5G网络中的接入设备或者未来演进的PLMN网络中的接入设备等，可以是WLAN中的接入点(access point，AP)，可以是NR系统中的gNB本申请实施例并不限定。
3、接入和移动性管理功能网元
接入和移动性管理功能网元主要用于移动性管理和接入管理等，可以用于实现移动性管理实体(mobility management entity，MME)功能中除会话管理之外的其它功能，例如，合法监听、或接入授权(或鉴权)等功能，此外还用于在UE与PCF之间传递用户策略。在本申请实施例中，可用于实现接入和移动管理网元的功能。
4、会话管理功能网元
会话管理功能网元主要用于会话管理、终端设备的网络互连协议(internet protocol，IP)地址分配和管理、选择可管理用户面功能(user plane function，UPF)网元、策略控制和收费功能接口的终结点以及下行数据通知等。在本申请实施例中，可用于实现会话管理网元的功能。
5、用户面功能网元
用户面功能网元可用于分组路由和转发、或用户面数据的QoS参数处理等。用户数据可通过该网元接入到数据网络(data network，DN)。在本申请实施例中，可用于实现用户面网元的功能，例如，在不同的UPF上建立会话时，UE的业务体验也会不同，因此需要上述SMF为UE的会话选择一个合适UPF。
6、策略控制网元
策略控制网元用于指导网络行为的统一策略框架，为控制平面功能网元(例如AMF，SMF网元等)提供策略规则信息等。主要负责针对会话、业务流级别进行计费、QoS带宽保障及移动性管理、UE策略决策等策略控制功能。在本申请实施例中，AMF与SMF所连接的PCF分别对应AM PCF(PCF for Access and Mobility Control)和SM PCF(PCF for Session Management)，在实际部署场景中可以是同一个PCF实体，也可以是是两个不同的PCF实体。
7、网络能力开放功能网元
网络能力开放功能网元用于向外部开放由3GPP网络功能提供的业务和网络能力信息(如终端位置、会话是否可达)等。
8、应用功能网元
应用功能网元主要用于传递应用侧对网络侧的需求，例如，QoS需求或用户状态事件订阅等。AF可以是第三方功能实体，也可以是运营商部署的应用服务，如IMS语音呼叫业务。对于第三方应用的应用功能实体，其与核心网进行交互时还可经由NEF进行授权处理，例如第三方应用功能直接向NEF发送请求消息，NEF判断该AF是否被允许发送该请求消息，若验证通过，则将转发该请求消息至对应PCF或统一数据管理(unified data management，UDM)。
9、统一数据管理网元
统一数据管理网元主要用于统一数据管理，支持3GPP认证和密钥协商机制中的认证信任状态处理，用户身份处理，接入授权，注册和移动性管理，签约管理，短消息管理等。
10、统一数据存储网元
统一数据存储网元主要用于签约数据、策略数据、应用数据等类型数据的存取功能。
11、数据网络
数据网络是指UE接入的某个特定的数据服务网络，例如，典型的DN包括因特网internet、IP多媒体子系统(IP multimedia subsystem，IPMS)。
在上述架构中，各接口功能描述如下：
N7：PCF与SMF之间的接口，用于下发PDU会话粒度以及业务数据流粒度控制策略。
N15：PCF与AMF之间的接口，用于下发UE策略及接入控制相关策略。
N5：AF与PCF之间的接口，用于应用业务请求下发以及网络事件上报。
N4：SMF与UPF之间的接口，用于控制面与用户面之间传递信息，包括控制面向用户面的转发规则、QoS控制规则、流量统计规则等的下发以及用户面的信息上报。
N11：SMF与AMF之间的接口，用于传递RAN和UPF之间的PDU会话隧道信息、传递发送给UE的控制消息、传递发送给RAN的无线资源控制信息等。
N2：AMF与RAN之间的接口，用于传递核心网侧至RAN的无线承载控制信息等。
N1：AMF与UE之间的接口，接入无关，用于向UE传递QoS控制规则等。
N8：AMF与UDM间的接口，用于AMF向UDM获取接入与移动性管理相关签约数据与鉴权数据，以及AMF向UDM注册UE当前移动性管理相关信息等。
N10：SMF与UDM间的接口，用于SMF向UDM获取会话管理相关签约数据，以及SMF向UDM注册UE当前会话相关信息等。
N35：UDM与UDR间的接口，用于UDM从UDR中获取用户签约数据信息。
N36：PCF与UDR间的接口，用于PCF从UDR中获取策略相关签约数据以及应用数据相关信息。
N52：UDM和NEF间的接口，用于NEF向第三方应用功能开放网络能力，如第三方应用功能通过NEF向UDM订阅特定群组中所有用户的可达性事件。
此外，NEF还与AMF、SMF均有直接接口，分别对应N29接口和N51接口(为简化图示，上图中并未展示)，用于开放运营商网络能力至第三方应用功能实体，前者可用于NEF直接向AMF订阅相应网络事件、更新用户配置信息，后者可用于更新SMF/UPF上的应用配置数据，如Application ID所对应的分组流描述信息(packet flow description， PFD)。
应理解，上述应用于本申请实施例的网络架构仅是举例说明的从传统点到点的架构和服务化架构的角度描述的网络架构，适用本申请实施例的网络架构并不局限于此，任何能够实现上述各个网元的功能的网络架构都适用于本申请实施例。
应理解，图2中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请对此不作具体限定。此外，上述各个网元之间的所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
需要说明的是，上述网元也可以称为实体、设备、装置或模块等，本申请并未特别限定。并且，在本申请中，为了便于理解和说明，在对部分描述中省略网元这一描述，例如，将SMF网元简称SMF，此情况下，该“SMF”应理解为SMF网元，以下，省略对相同或相似情况的说明。
可以理解的是，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选的，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
还应理解，在图2所示的通信系统中，各组成网元的功能仅为示例性的，各个组成网元在应用于本申请的实施例中时，并非全部功能都是必需的。
此外，如图2中包括的各个网元(比如PCF、AMF等)的命名仅是一个名字，名字对网元本身的功能不构成限定。在5G网络以及未来其它的网络中，上述各个网元也可以是其他的名字，本申请实施例对此不作具体限定。例如，在6G网络中，上述各个网元中的部分或全部可以沿用5G中的术语，也可能是其他命名，等等，在此进行统一说明，以下不再赘述。
还需说明的是，图2中控制面功能的各个网元之间的通信是以非服务化接口为例进行描述，但是并不对本申请实施例的保护范围构成限定的。本领域技术人员可以理解，图2中控制面功能的各个网元也可以通过服务化接口进行通信，比如，AMF对外提供的服务化接口可以为Namf；SMF提供的服务化接口可以为Nsmf；UDM对外提供的服务化接口可以为Nudm，AF提供的服务化接口可以为Naf；PCF对外提供的服务化接口可以为Npcf等等。
上述图2中的网元是基于参考点的架构，并不对本申请实施例构成限定。图3给出了基于服务化接口的架构示意图。如图3所示，该按架构包括：NSSF、AUSF、UDM、NEF、NRF、PCF、AF、AMF、SMF、UE、RAN、UPF、DN。在图3中，NSSF对外提供的服务化接口可以为Nnssf，NEF对外提供的服务化接口可以为Nnef，NRF对外提供的服务化接口可以为Nnrf，AMF对外提供的服务化接口可以为Namf；SMF提供的服务化接口可以为Nsmf；UDM对外提供的服务化接口可以为Nudm，AF提供的服务化接口可以为Naf；PCF对外提供的服务化接口可以为Npcf，AUSF对外提供的服务化接口可以为Nausf，CHF对外提供的服务化接口可以为Nchf；控制面功能与RAN和UPF间的接口是非服务化接口。UE通过N1接口与AMF连接，UE通过无线资源控制(radio resource control，RRC)协议与RAN连接；RAN通过N2接口与AMF连接，RAN通过N3接口与UPF连接；UPF通过N6接口与DN连接，同时，UPF通过N4接口与SMF连接。相关描述可以参考标准 中的5G系统架构(5G system architecture)，为了简洁，这里对架构300的连接关系不作赘述。
为了便于理解本申请的实施例，首先以5G网路为例对UE建立PDU会话连接以及PDU会话管理的过程简单说明。
在5G网络中，5G网络为UE和DN网络提供数据交换服务，该服务称为PDU连接服务。UE通过向移动网络发起PDU会话建立请求获得PDU连接服务。网络侧通过为UE维护PDU会话以提供PDU连接服务。
为实现UE与DN网络之间的数据交换，UE需要使用移动网络提供的PDU连接服务，建立基于DNN的PDU会话(信令面流程)。PDU会话的建立包括两个基本过程：UE向移动网络注册入网流程、UE向网络请求建立PDU会话流程，这两个过程属于UE与移动网络的信令面交互流程。
通用的UE注册入网流程可简单描述为：UE通过(R)AN发送注册请求至AMF，AMF根据用户标识向特定UDM获取签约数据。网络侧经过一系列鉴权、授权操作最终确认允许UE接入网络，此时AMF响应UE注册请求，并向UE下发相关策略信息，UE完成网络注册驻留。网络侧AMF维护UE的注册入网信息，对UE进行移动性管理。
UE完成注册入网后，可发起PDU会话建立请求，获取网络的PDU连接服务。通用的PDU会话建立流程可简单描述为：UE通过RAN发送PDU会话建立请求到AMF，AMF选择SMF为UE提供会话服务，保存SMF与PDU会话的对应关系，并将会话建立请求发送至SMF，SMF为UE选择相应UPF建立用户面传输路径，并为其分配IP地址。
在对UE进行PDU会话管理过程中，SMF通过N4接口与UPF交互，控制UPF创建、修改、删除相应的UE N4会话(N4 Session/PFCP Session)实现对UPF处理数据报文的控制。SMF对UPF内的UE N4会话下发各类数据包处理规则完成对UPF处理数据包的控制。UPF收到外部数据报文后，根据SMF下发的数据报文匹配规则进报文匹配，根据转发规则转发报文。
为了便于理解本申请实施例，作出以下几点说明。
第一，在本申请实施例中，“用于指示”可以包括用于直接指示和用于间接指示，也可以包括显式指示和隐式指示。将某一信息(如下文所述的配置信息)所指示的信息称为待指示信息，则具体实现过程中，对待指示信息进行指示的方式有很多种，例如但不限于，可以直接指示待指示信息，如待指示信息本身或者该待指示信息的索引等。也可以通过指示其他信息来间接指示待指示信息，其中该其他信息与待指示信息之间存在关联关系。还可以仅仅指示待指示信息的一部分，而待指示信息的其他部分则是已知的或者提前约定的。例如，还可以借助预先约定(例如协议规定)的各个信息的排列顺序来实现对特定信息的指示，从而在一定程度上降低指示开销。
第二，在下文示出的实施例中第一、第二、第三、第四以及各种数字编号仅为描述方便进行的区分，并不用来限制本申请实施例的范围。例如，区分不同的消息等。
第三，本申请实施例中涉及的“保存”，可以是指的保存在一个或者多个存储器中。所述一个或者多个存储器，可以是单独的设置，也可以是集成在编码器或者译码器，处理器、或通信装置中。所述一个或者多个存储器，也可以是一部分单独设置，一部分集成在译码器、处理器、或通信装置中。存储器的类型可以是任意形式的存储介质，本申请并不 对此限定。
第四，本申请实施例中涉及的“协议”可以是指通信领域的标准协议，例如可以包括LTE协议、NR协议以及应用于未来的通信系统中的相关协议，本申请对此不做限定。
第五，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a、b和c中的至少一项(个)，可以表示：a，或b，或c，或a和b，或a和c，或b和c，或a、b和c，其中a，b，c可以是单个，也可以是多个。
第六，本申请的以下的实施例中，以UE作为终端设备进行介绍的，但本申请的终端设备并不限于此。
第七、为便于理解本申请所提供的通信的方法，以下，不失一般性，以两个终端设备为例详细说明本申请实施例提供的方法。
图4示出了本申请提供的一种通信的方法的一例示意性流程图。以下结合各步骤，将该接入业务方法400应用于上述图1至图3所示的网络架构中。
S401，终端中央处理器(central processing unit，CPU)/用户向UE1和UE2发送冗余配置。
具体地，可以是当UE1、UE2分别插入签约用户sim卡后，终端CPU/用户向UE1和UE2发送冗余配置。冗余配置可以包括：冗余指示，冗余类型、冗余标识。
或者，可选地，终端CPU/用户向UE1和UE2发送冗余配置可以在UE1、UE2分别插入签约用户sim卡之前。
其中，冗余指示用于指示开启该UE1、UE2的冗余传输，或者，该冗余指示也可以理解为，用于指示将后续网络设备需要将该UE1和UE2设置为冗余传输的设备。该冗余类型可以是冗余收发使用的类型，例如，可以包括多发选收、主备传输或多链路负载均衡传输等冗余传输采用的协议类型及相关参数。冗余标识，是冗余结对的UE在网络设备侧的唯一标识信息，应理解，形成结对的多个UE拥有相同的冗余标识。
需要说明的是，该终端CPU可以指无线终端内对无线通信模组，例如，无线通信芯片等，进行自动化配置的执行模块。
该用户可以是操作配置无线通信终端的外部系统，例如可以是操作终端设备的人等。
S402，UE1和UE2完成注册入网。
具体地，终端CPU/用户通过设备上电或者通过命令拨号入网等方式，触发UE1和UE2注册入网。随后UE1和UE2分别发起网络注册，驻留到无线网络，该过程可参考3GPP相关入网协议，本申请为了说明的简便性，在此不再赘述。
S403，UE1和UE2分别向AMF发送第一PDU会话请求和第二PDU会话请求。
具体地，UE1和UE2分别向AMF发起PDU会话请求，其中，该第一PDU会话请求和第二PDU会话请求携带相同的冗余传输配置信息。具体地，该第一PDU会话请求可以携带UE1的用户签约标识，冗余指示，冗余类型以及冗余标识，第二PDU会话请求可以携带UE1的用户签约标识，冗余指示，冗余类型以及冗余标识。
S404，AMF为UE1和UE2确定相同的SMF。
具体地，AMF收到UE1和UE2发送的第一PDU会话请求和第二PDU会话请求后，AMF根据第一PDU会话请求和第二PDU会话请求中携带的冗余标识，为UE1签约用户和UE2签约用户选择相同的SMF。
S405，AMF向SMF发送UE1的第一PDU会话请求，和UE2的第二PDU会话请求。
具体地，AMF分别向SMF发送UE1和UE2的第一PDU会话请求和第二PDU会话请求，该UE1的第一PDU会话请求用于请求为UE1创建分组数据单元PDU会话，该UE2的第二PDU会话请求用于请求为UE2创建分组数据单元PDU会话，其中，该第一PDU会话请求可以携带UE1的用户签约标识，冗余指示，冗余类型以及冗余标识，第二PDU会话请求可以携带UE2的用户签约标识，冗余指示，冗余类型以及冗余标识。
S406，第一SMF为UE1和UE2确定UPF。
具体地，第一SMF根据UE1的第一PDU会话请求，和UE2的第二PDU会话请求，为UE1和UE2确定相同的UPF。其中，SMF可以根据UE1和UE2的冗余标识，为UE1和UE2选择相同的UPF。该选择UPF的过程可以参考3GPP相关会话创建流程，本申请不做限定。
S407，SMF向UPF发送创建第一PDU会话上下文请求和创建第二PDU会话上下文请求。
具体地，SMF为UE1和UE2确定UPF后，向UPF发送UE1的创建第一PDU会话上下文请求和UE2的创建第二PDU会话上下文请求，其中，该创建第一PDU会话上下文请求和创建第二PDU会话上下文请求携带冗余传输配置信息。
S408，UPF创建冗余上下文。
具体地，当UPF收到创建第一PDU会话上下文请求或创建第二PDU会话上下文请求后，UPF为第一UE创建冗余上下文，并获取该冗余上下文的冗余上下文标识。
需要说明的是，该第一UE为UPF接收到的首个创建PDU会话上下文的UE，应理解，UPF接收各个UE的创建PDU会话上下文请求时，由于各具体UE的上线时间有差异，或者是SMF发送的创建PDU会话上下文请求会被UPF在不同的时间接收，因此，UPF只需为首个接收到的创建PDU会话上下文请求对应的UE创建冗余上下文，并获取冗余上下文标识。若UPF先接收到创建第一PDU会话上下文请求，则UE1为第一UE，或者，UPF先接收到创建第二PDU会话上下文请求，则UE2为第一UE。
其中，该冗余上下文用于处理UE1或UE2冗余报文，例如多发选收场景，冗余上下文负责对下行报文进行冗余复制并通过UE1或UE2上下文进行多发，对UE1或UE2上行冗余报文进行冗余去重后转发。
需要说明的是，在本申请实施例中，冗余上下文也可以称为冗余传输上下文。
S409，UPF为UE1和UE2创建PDU会话上下文。
当UPF创建好冗余上下文后，UPF为UE1和UE2创建PDU会话上下文，获取该PDU会话上下文标识，并将该UE1和UE2的PDU会话上下文标识添加到冗余上下文中。
具体地，当UPF完成冗余上下文创建后，该UPF继续创建第一UE的PDU会话，当第一UE的PDU会话创建成功后，该UPF获取该PDU会话上下文标识并将该第一UE的PDU会话上下文标识添加到冗余上下文中。随后，等该UPF接收到第二个UE创建PDU 会话请求后，UPF根据创建PDU会话请求携带的信息确定该第二个UE结对的UE1已经创建过PDU会话，对应的冗余上下文也已经存在，此时该UPF直接创建UE2的PDU会话上下文，并获取该第二PDU会话上下文标识，并将该UE2对应PDU会话上下文标识与冗余上下文关联。
其中，可以是UPF为UE1和UE2创建N4会话上下文，并获取该N4会话上下文标识。
S410，UPF向SMF发送第一响应消息和第二响应消息。
具体地，当第一UPF为UE1和UE2创建PDU会话上下文后，该UPF向SMF发送第一响应消息和第二响应消息，其中，第一响应消息携带UE1的PDU会话标识，第二响应消息携带UE2的PDU会话标识。
在一种可实现的方式中，本申请提供的通信的方法400还可以包括其他步骤：
S411，SMF分别向UE1和UE2发送创建会话响应消息。
具体地，当UE1和UE2的PDU会话创建成功后，该SMF分别向UE1和UE2发送创建会话响应消息。
可选地，该方法400还可以包括二次鉴权过程，该过程可以包括：
S412，SMF分别向DN-AAA发送二次鉴权请求消息。
具体地，当SMF收到UE1和UE2的第一请求消息后，该SMF根据本地配置、UE1和UE2用户签约标识以及冗余指示决定是否向该DN-AAA发送二次鉴权请求消息。当确定发起二次鉴权过程时，该二次鉴权请求消息中携带用户标识，例如可以是一般公共订阅标识符(generic public subscription identifier，GPSI)，该用户标识可以用于DN-AAA识别待鉴权用户，该二次鉴权请求消息中还可以携带冗余指示，冗余类型以及冗余标识。
可选地，SMF也可根据本地配置，决策是否允许UE1签约用户和UE2签约用户组成冗余传输结对。
S413，DN-AAA对UE1和UE2鉴权。
具体地，DN-AAA根据本地配置确认UE1和UE2对应的用户标识是否允许启用冗余传输，UE1和UE2对应的用户标识是否允许结对，如果允许结对则发起对UE1/UE2鉴权。
可选地，如果DN-AAA确认UE1和UE2不允许结对，则直接向SMF发送二次鉴权失败响应，此时UE1、UE2会话建立失败。
S414，DN-AAA向SMF发送鉴权响应消息。
具体地，DN-AAA对UE1和UE2鉴权成功后，记录冗余标识与UE1签约用户、UE2签约用户绑定关系，向SMF发送二次鉴权成功响应消息，确认UE1、UE2签约用户可相互结对启用冗余传输。
基于本申请的实施例，在NAS信令流程中，实现冗余传输与UE设备绑定，与UE签约用户解耦，在UE创建PDU会话阶段完成签约用户结对互为冗余传输的动态关联，实现设备冗余收发与SIM无关。
图5示出了本申请提供的一种通信的方法的一例示意性流程图。以下结合各步骤，将该接入业务方法500应用于上述图1至图3所示的网络架构中。
S501至S506，可对应参照上述图4流程中的相关说明，为了简便，本申请在此不再赘述。
S507，SMF向UPF发送第一请求消息。
第一请求消息用于请求为UE1和UE2创建冗余传输上下文。
S508，UPF创建冗余上下文。
具体地，该UPF收到SMF发送的第一请求消息后，为UE1和UE2创建冗余上下文。
S509，UPF向SMF发送第一请求消的响应消息。
该第一请求消息的响应消息携带冗余传输上下文标识。
S510，SMF向UPF发送创建第一PDU会话上下文请求和创建第二PDU会话上下文请求。
具体地，SMF向UPF发送UE1的创建第一PDU会话上下文请求和UE2的创建第二PDU会话上下文请求，其中，该创建第一PDU会话上下文请求和创建第二PDU会话上下文请求携带冗余传输配置信息和冗余传输上下文标识。
S511，UPF创建PDU会话上下文。
具体地，当UPF收到第一PDU会话上下文请求和创建第二PDU会话上下文请求后，UPF分别为UE1和UE2创建PDU会话，并获取该PDU会话的上下文标识，其中该PDU会话可以是N4会话。
S512，UPF向SMF发送第一响应消息和第二响应消息。
具体地，当第一UPF为UE1和UE2创建PDU会话上下文后，该UPF向SMF发送第一响应消息和第二响应消息，其中，第一响应消息携带UE1的PDU会话标识，第二响应消息携带UE2的PDU会话标识。
S513，SMF向UPF发送第一修改请求和第二修改请求。
具体地，第一修改请求消息携带UE1的PDU会话标识，第二修改请求携带UE2的PDU会话标识，第一修改请求用于指示将UE1的PDU会话标识添加到冗余传输上下文中，第二修改请求用于指示将UE2的PDU会话标识添加到所述冗余传输上下文中。
S514，UPF修改冗余上下文。
具体地，当UPF收到第一修改请求和第二修改请求后，UPF根据第一修改请求将UE1的PDU会话标识添加到冗余传输上下文中，根据第二修改请求将UE2的PDU会话标识添加到所述冗余传输上下文中。
在一种可实现的方式中，本申请提供的通信的方法500还可以包括其他步骤：
S515-S518，该过程可相应的参考图4的相关说明，在此不再赘述。
基于本申请的实施例，在NAS信令流程中，利用指示信息指示将UE的会话标识添加到冗余上下文中，实现冗余传输与UE设备绑定，与UE签约用户解耦，在UE创建PDU会话阶段完成签约用户结对互为冗余传输的动态关联，实现设备冗余收发与SIM无关。
当利用上述图4或图5所述的方法完成通信后，本申请的通信的方法还包括对该结对用户解约的方法。图6示出了基于NAS信令流程来实现签约用户结对解约的流程示意图，该方法600包括：
S601，UE1触发会话删除。
具体地，当SIM从UE1拔除时，UE1触发会话删除流程，例如可以是UE1下签约用户SIM卡从UE1上拔除，插入到UE3中。
S602，第一SMF向第一UPF发送第一删除消息。
具体地，第一SMF向第一UPF发送第一删除消息，该第一删除消息用于指示该第一UPF删除该UE1的N4会话上下文。
S603，第一SMF向第一UPF发送第二删除消息。
具体地，第一SMF向第一UPF发送第二删除消息，该第二删除消息用于指示该第一UPF删除冗余传输上下文或删除冗余传输上下文UE1的用户签约标识。其中，该第二删除消息中可以携带UE1的N4会话的上下文标识。
在一种可实现的方式中，若该UE1的N4会话不是冗余上下文中的最后一个会话，该第二删除消息用于指示该第一UPF删除冗余上下文中的UE1的用户签约标识。
在另一种可实现的方式中，若该UE1的N4会话是冗余上下文中的最后一个会话，该第二删除消息用于指示该第一UPF删除冗余上下文。
在一种可实现的方式中，本申请提供的通信的方法600还可以包括其他步骤：
S604，第一SMF向DN-AAA发送指示信息。
具体地，对应于二次鉴权流程，当UE1触发会话删除流程后，第一SMF向DN-AAA发送指示信息，该指示信息用于指示UE1触发会话删除。
S605，DN-AAA解除冗余标识和UE1的绑定关系。
具体地，当DN-AAA确定该UE1触发了会话删除时，该DN-AAA解除冗余标识和UE1的绑定关系。
需要说明的是，如果冗余标识中所有的UE信息均被删除，则DN-AAA清除冗余标识相关记录。
S606，第一SMF向UE1发送响应消息。
具体地，当第一SMF与第一UPF完成删除UE1上下文信息后，向UE1发送响应消息。用于通知UE1已经完成UE1的会话删除。
基于本申请的实施例，在NAS信令流程中，实现了在UE PDU会话释放阶段动态解除UE会话冗余传输。
图7示出了本申请提供的一种通信的方法的一例示意性流程图。以下结合各步骤，将该接入业务方法700应用于上述图1至图3所示的网络架构中。
S701，终端CPU/用户从UE1和UE2处获取设备标识，该设备标识可以是国际移动设备识别码(international mobile equipment identity，IMEI)，用于在网络中识别每一个UE。
S702，终端CPU/用户向AF发送UE1和UE2的设备结对请求消息。
具体地，该设备结对请求消息携带UE1和UE2的设备标识以及冗余类型。
需要说明的是，该UE1和UE2的设备标识用于标识设备，并不是UE1和UE2的签约用户标识信息。
S703，AF将UE1和UE2设备结对。
具体地，该AF保存UE1和UE2设备冗余结对绑定关系，并为结对设备分配冗余标识，同时保持冗余标识关联的UE1和UE2设备标识，冗余类型。
S704，终端CPU/用户从UE1和UE2分别获取入网签约用户标识。
具体地，该入网签约用户标识可以例如是一般公共订阅标识符(generic public subscription identifier，GPSI)。
S705，终端CPU/用户向AF发送设备绑定签约用户请求。
具体地，该请求消息中携带UE1和UE2关联的用户标识以及设备标识。
S706，AF保存UE1和UE2设备标识和用户标识绑定关系
S707，AF向NEF发送冗余配置请求信息。
具体地，该冗余配置请求信息包括第一指示信息或第二指示信息，该第一指示信息用于指示NEF添加第一冗余配置信息，该第二指示信息用于指示NEF删除第二冗余配置信息。
在一种可实现的方式中，若AF记录的信息中，冗余设备和签约用户关联关系是首次绑定，则AF向NEF下发的冗余配置请求消息包括第一指示信息，该第一指示信息用于指示NEF添加第一冗余配置信息，该第一冗余配置信息包括：UE1和UE2用户标识，例如，GPSI，冗余指示信息，冗余类型以及冗余标识。
在另一种可实现的方式中，若AF记录的信息中，冗余设备和签约用户关联关系是变更关系，则AF向NEF冗余配置请求消息包括第二指示信息，该第二指示信息用于指示NEF删除第二冗余配置信息，其中，该第二冗余配置信息包括：UE1和UE2用户标识，即用于指示删除配置的用户，冗余标识，用于指示UE1和UE2用户从指示的冗余标识中解除冗余传输。
可选地，当AF向NEF发送了包括第二指示信息的冗余配置请求消息后，该AF还可以向NEF发送包括第一指示信息的冗余配置请求消息。
S708，NEF向UDM发送修改签约数据请求。
具体地，NEF收到AF冗余配置请求后，NEF向UDM发送修改签约数据请求。
S709，UDM修改签约数据。
具体地，UDM收到修改签约数据请求后，按请求修改签约数据。
在一种可实现的方式中，若NEF根据第一指示信息向UDM发送修改签约数据请求，则该修改签约数据请求用于指示UDM添加UE1和UE2的第一冗余配置信息。
在一种可实现的方式中，若NEF根据第二指示信息向UDM发送修改签约数据请求，则该修改签约数据请求用于指示UDM删除UE1和UE2的的第二冗余配置信息。
S710，UDM向SMF发送签约数据变更消息。
具体地，对于已经创建会话的UE1和UE2，UDM向SMF发送签约数据变更消息，指示该UE的签约数据发生变更。
S711，SMF向UE发送签约数据变更消息。
具体地，该签约数据变更消息用于通知UE1和UE2下线受影响的会话，并重新发起会话建立。
S712，NEF向AF发送响应消息。
具体地，该响应消息包括冗余结对配置结果。
S713，AF向NEF订阅签约用户标识与设备标识关联关系变更通知。
具体地，在增加冗余结对配置的场景下，AF向NEF订阅签约用户标识与设备标识关联关系变更通知。
S714，NEF向AF发送变更通知。
具体地，当签约用户与设备标识关联关系发生变更时，NEF向AF发送变更通知。
S715，UE1和UE2分别向AMF发送PDU会话建立请求消息。
具体地，UE1和UE2分别向AMF发起PDU会话建立请求消息。
S716，AMF向UDM获取签约用户数据。
具体地，该获取过程可参考当前相关技术说明，在此不再赘述。其中该签约用户数据可以包括：UE1和UE2签约冗余指示，冗余标识，冗余类型等。
S717，AMF为UE1和UE2确定SMF。
具体地，AMF根据获取的冗余标识，为UE1签约用户和UE2签约用户选择相同的SMF。
S718，AMF向SMF发送UE1的第一PDU会话请求，和UE2的第二PDU会话请求。
具体地，AMF分别向SMF发送UE1和UE2的第一PDU会话请求和第二PDU会话请求，该UE1的第一PDU会话请求用于请求为UE1创建分组数据单元PDU会话，该UE2的第二PDU会话请求用于请求为UE2创建分组数据单元PDU会话，其中，该第一PDU会话请求可以携带UE1的用户签约标识，第二PDU会话请求可以携带UE2的用户签约标识。
S719，SMF向UDM获取签约用户数据。
具体地，该获取过程可参考当前相关技术说明，在此不再赘述。其中该签约用户数据可以包括：UE1和UE2签约冗余指示，冗余标识，冗余类型等。
S720，SMF为UE1和UE2确定UPF。
具体地，SMF根据获取的冗余标识，为UE1签约用户和UE2签约用户选择相同的UPF。
S721，SMF向UPF发送创建第一PDU会话上下文请求和创建第二PDU会话上下文请求。
具体地，SMF为UE1和UE2确定UPF后，向UPF发送UE1的创建第一PDU会话上下文请求和UE2的创建第二PDU会话上下文请求，其中，该创建第一PDU会话上下文请求和创建第二PDU会话上下文请求携带冗余传输配置信息。
S722，UPF创建冗余上下文。
当UPF收到创建第一PDU会话上下文请求或创建第二PDU会话上下文请求后，UPF为第一UE创建冗余上下文，并获取该冗余上下文的冗余上下文标识。
需要说明的是，该第一UE为UPF接收到的首个创建PDU会话上下文的UE，应理解，UPF接收各个UE的创建PDU会话上下文请求时，由于各具体UE的上线时间有差异，或者是SMF发送的创建PDU会话上下文请求会被UPF在不同的时间接收，因此，UPF只需为首个接收到的创建PDU会话上下文请求对应的UE创建冗余上下文，并获取冗余上下文标识。若UPF先接收到创建第一PDU会话上下文请求，则UE1为第一UE，或者，UPF先接收到创建第二PDU会话上下文请求，则UE2为第一UE。
其中，该冗余上下文用于处理UE1或UE2冗余报文，例如多发选收场景，冗余上下文负责对下行报文进行冗余复制并通过UE1或UE2上下文进行多发，对UE1或UE2上行冗余报文进行冗余去重后转发。
需要说明的是，在本申请实施例中，冗余上下文也可以称为冗余传输上下文。
S723，UPF为UE1和UE2创建PDU会话上下文。
当UPF创建好冗余上下文后，UPF为UE1和UE2创建PDU会话上下文，获取该PDU 会话上下文标识，并将该UE1和UE2的PDU会话上下文标识添加到冗余上下文中。
具体地，当UPF完成冗余上下文创建后，该UPF继续创建第一UE的PDU会话，当第一UE的PDU会话创建成功后，该UPF获取该PDU会话上下文标识并将该第一UE的PDU会话上下文标识添加到冗余上下文中。随后，等该UPF接收到第二个UE创建PDU会话请求后，UPF根据创建PDU会话请求携带的信息确定该第二个UE结对的UE1已经创建过PDU会话，对应的冗余上下文也已经存在，此时该UPF直接创建UE2的PDU会话上下文，并获取该第二PDU会话上下文标识，并将该UE2对应PDU会话上下文标识与冗余上下文关联。
其中，可以是UPF为UE1和UE2创建N4会话上下文，并获取该N4会话上下文标识。
S724，UPF向SMF发送第一响应消息和第二响应消息。
具体地，当第一UPF为UE1和UE2创建PDU会话上下文后，该UPF向SMF发送第一响应消息和第二响应消息，其中，第一响应消息携带UE1的PDU会话标识，第二响应消息携带UE2的PDU会话标识。
在一种可实现的方式中，本申请提供的通信的方法700还可以包括其他步骤：
S725，SMF分别向UE1和UE2发送创建会话响应消息。
具体地，当UE1和UE2的N4会话创建成功后，该SMF分别向UE1和UE2发送创建会话响应消息。
基于本申请的实施例，在基于网络能力开放流程中，实现冗余传输与UE设备绑定，与UE签约用户解耦，在UE创建PDU会话阶段完成签约用户结对互为冗余传输的动态关联，实现设备冗余收发与SIM无关。
图8示出了本申请提供的一种通信的方法的一例示意性流程图。以下结合各步骤，将该接入业务方法800应用于上述图1至图3所示的网络架构中。
需要说明的是，图8是基于网络能力开放流程中实现设备冗余传输的。
为了说明的简便，仅对图8的步骤与上述实施例进行对应说明。
其中在图8中，步骤801至步骤820可以参考图7中的步骤701至步骤720，步骤821至步骤828可以参考图5中对应的步骤507至步骤514，步骤829可以参照图7的步骤725。
当利用上述图7或图8所述的方法完成通信后，本申请的通信的方法还包括对该结对用户解约的方法。图9示出了基于网络能力开放流程来实现签约用户结对解约的流程示意图，该方法900包括：
S901，UE1触发会话删除。
具体地，当SIM从UE1拔除时，UE1触发会话删除流程，例如可以是UE1下签约用户SIM卡从UE1上拔除，插入到UE3中。
S902，SMF向UPF发送第一删除消息。
具体地，该第一删除信息用于指示删除UE1的N4会话上下文。
S903，SMF向UPF发送第二删除消息。
具体地，SMF向UPF发送第二删除消息，该第二删除消息用于指示该UPF删除冗余传输上下文或删除冗余传输上下文UE1的用户签约标识。其中，该第二删除消息中可以携带UE1的N4会话的上下文标识。
在一种可实现的方式中，若该UE1的N4会话不是冗余上下文中的最后一个会话，该第二删除消息用于指示该UPF删除冗余上下文中的UE1的用户签约标识。
在另一种可实现的方式中，若该UE1的N4会话是冗余上下文中的最后一个会话，该第二删除消息用于指示该UPF删除冗余上下文。
S904，SMF向UDM发送第三删除消息。
具体地，SMF调用UDM Nudm_UECM_Deregistration接口，删除会话关联信息该过程可以参考3GPP相关流程，本申请不做赘述。
S905，UDM通过NEF向AF发送第一变更消息。
具体地，该第一变更消息用于通知AF，UE1的用户标识和设备标识关系发生变更。
可选地，该第一变更消息可以携带指示信息，该指示信息用于指示AF删除UE1的N4会话。
S906，AF删除UE1设备标识和用户标识的关联关系。
S907，AF向NEF发送第一指示信息。
具体地，AF调用NEF接口向NEF发送第一指示信息，该第一指示信息用于指示NEF删除冗余配置，该冗余配置包括：用户标识，冗余标识。
S908，NEF向UDM发送第二指示信息。
具体地，NEF调用UDM接口向UDM发送第二指示信息，该第二指示信息用于指示UDM删除用户标识指定的签约数据中，冗余传输相关配置，例如，删除冗余指示，冗余类型，冗余标识等。
S909，AF向NEF发送第二变更消息。
具体地，AF向NEF发送第二变更消息，该第二变更消息用于指示NEF取消订阅UE1用户标识和变更设备标识关联关系，该第二变更消息中可以携带用户标识信息。
针对于上述图4至图9的实施例，需要说明的是：
(1)实施例所描述的各个流程图的步骤编号仅为执行流程的一种示例，并不构成对步骤执行的先后顺序的限制，本申请实施例中相互之间没有时序依赖关系的步骤之间没有严格的执行顺序。此外，各个流程图中所示意的步骤并非全部是必须执行的步骤，可以根据实际需要在各个流程图的基础上增添或者删除部分步骤。
(2)上述图4至图9的实施例可以独立实施，也可以互相结合，例如，图4所示实施例和图6所示实施例互相结合，图8所示实施例和图9所示实施例互相结合等。
(3)上述实施例中采用了一些5G通信系统中的消息和参数，但在具体实施中，可能使用不同的消息或消息名称，本申请实施例对此不做限制。
以上，结合图4至图9详细说明了本申请实施提供的通信的方法方法，以下，结合图10和图11详细说明本申请实施例提供的通信装置。
图10为本申请实施例提供的可能的通信装置的结构示意图。如图10所示，通信装置1000包括处理单元1010和收发单元1020。
通信装置1000用于实现上述图4至图9所示的方法实施例中SMF的功能或操作的模块，或者该通信装置1000用于实现上述图4至图9所示的方法实施例中AMF的功能或操作的模块，或者该通信装置1000用于实现上述图7至图9所示的方法实施例中AF的功能或操作的模块，或者该通信装置1000用于实现上述图7至图9所示的方法实施例中NEF 的功能或操作的模块，该模块可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。
当通信装置1000用于实现图4所示的方法实施例中SMF的功能时，收发单元1020用于接收来自第一终端设备的第一PDU会话请求，和第二终端设备的第二PDU会话请求，其中，第一PDU会话请求和第二PDU会话请求携带相同的冗余传输配置信息；向用户面功能实体UPF发送创建第一PDU会话上下文请求和创建第二PDU会话上下文请求，创建第一PDU会话上下文请求和创建第二PDU会话上下文请求携带冗余传输配置信息；以及接收来自UPF的第一响应消息和第二响应消息，第一响应消息携带第一终端设备的PDU会话标识，第二响应消息携带第二终端设备的PDU会话标识。
当通信装置1000用于实现图5所示的方法实施例中SMF的功能时，收发单元1020用于接收来自第一终端设备的第一PDU会话请求，和第二终端设备的第二PDU会话请求，其中，第一PDU会话请求和第二PDU会话请求携带相同的冗余传输配置信息；向用户面功能实体UPF发送创建第一PDU会话上下文请求和创建第二PDU会话上下文请求，创建第一PDU会话上下文请求和创建第二PDU会话上下文请求携带冗余传输配置信息；以及接收来自UPF的第一响应消息和第二响应消息，第一响应消息携带第一终端设备的PDU会话标识，第二响应消息携带第二终端设备的PDU会话标识。
当通信装置1000用于实现图6所示的方法实施例中SMF的功能时，收发单元1020用于向UPF发送第一删除消息和第二删除消息，其中，第一删除消息用于指示删除N4上下文，第二删除消息用于指示删除冗余传输上下文中的用户签约标识和/或删除冗余传输上下文。
当通信装置1000用于实现图7所示的方法实施例中SMF的功能时，处理单元1010用于根据第一PDU会话请求向统一数据管理UDM获取第一终端设备的第一冗余传输配置信息，以及，根据第二PDU会话请求向UDM获取第二终端设备的第二冗余传输配置信息。收发单元1020用于接收来自第一终端设备的第一PDU会话请求，和第二终端设备的第二PDU会话请求，向用户面功能实体UPF发送创建第一PDU会话上下文请求和创建第二PDU会话上下文请求，其中，创建第一PDU会话上下文请求携带第一冗余传输配置信息，创建第二PDU会话上下文请求携带第二冗余传输配置信息，以及接收来自UPF的第一响应消息和第二响应消息，第一响应消息携带第一终端设备的PDU会话标识，第二响应消息携带第二终端设备的PDU会话标识。
当通信装置1000用于实现图8所示的方法实施例中SMF的功能时，处理单元1010用于根据第一PDU会话请求向统一数据管理UDM获取第一终端设备的第一冗余传输配置信息，以及，根据第二PDU会话请求向UDM获取第二终端设备的第二冗余传输配置信息。收发单元1020用于接收来自第一终端设备的第一PDU会话请求，和第二终端设备的第二PDU会话请求，向用户面功能实体UPF发送创建第一PDU会话上下文请求和创建第二PDU会话上下文请求，其中，创建第一PDU会话上下文请求携带第一冗余传输配置信息，创建第二PDU会话上下文请求携带第二冗余传输配置信息，以及接收来自UPF的第一响应消息和第二响应消息，第一响应消息携带第一终端设备的PDU会话标识，第二响应消息携带第二终端设备的PDU会话标识。
当通信装置1000用于实现图9所示的方法实施例中SMF的功能时，收发单元1020 用于向UPF发送第一删除消息和第二删除消息。其中，第一删除消息用于指示删除PDU上下文，第二删除消息用于指示删除冗余传输上下文中的用户签约标识和/或删除冗余传输上下文。
当通信装置1000用于实现图4所示的方法实施例中AMF的功能时，处理单元1010用于根据冗余传输配置信息为第一终端设备和第二终端设备确定相同的会话管理功能网元SMF。收发单元1020用于接收来自第一终端设备的第一PDU会话请求，和第二终端设备的第二PDU会话请求，其中，所述第一PDU会话请求和所述第二PDU会话请求携带相同的冗余传输配置信息，以及向SMF发送第一PDU会话请求和第二PDU会话请求。
当通信装置1000用于实现图5所示的方法实施例中AMF的功能时，处理单元1010用于根据冗余传输配置信息为第一终端设备和第二终端设备确定相同的会话管理功能网元SMF。收发单元1020用于接收来自第一终端设备的第一PDU会话请求，和第二终端设备的第二PDU会话请求，其中，所述第一PDU会话请求和所述第二PDU会话请求携带相同的冗余传输配置信息，以及向SMF发送第一PDU会话请求和第二PDU会话请求。
当通信装置1000用于实现图7所示的方法实施例中AMF的功能时，处理单元1010用于根据冗余传输配置信息为第一终端设备和第二终端设备确定相同的会话管理功能网元SMF。收发单元1020用于接收来自第一终端设备的第一PDU会话请求，和第二终端设备的第二PDU会话请求，以及向SMF发送第一PDU会话请求和第二PDU会话请求。
当通信装置1000用于实现图8所示的方法实施例中AMF的功能时，处理单元1010用于根据冗余传输配置信息为第一终端设备和第二终端设备确定相同的会话管理功能网元SMF。收发单元1020用于接收来自第一终端设备的第一PDU会话请求，和第二终端设备的第二PDU会话请求，以及向SMF发送第一PDU会话请求和第二PDU会话请求。
当通信装置1000用于实现7所示的方法实施例中AF的功能时，处理单元1010用于获取第一配置信息；收发单元1020基于第一配置信息向NEF发送冗余配置请求消息，该冗余配置请求消息包括第一指示信息或第二指示信息，其中，第一指示信息用于指示NEF添加第一冗余配置信息，第二指示信息用于指示NEF删除第二冗余配置信息。
当通信装置1000用于实现8所示的方法实施例中AF的功能时，处理单元1010用于获取第一配置信息；收发单元1020基于第一配置信息向NEF发送冗余配置请求消息，该冗余配置请求消息包括第一指示信息或第二指示信息，其中，第一指示信息用于指示NEF添加第一冗余配置信息，第二指示信息用于指示NEF删除第二冗余配置信息。
当通信装置1000用于实现图9所示的方法实施例中NEF的功能时，处理单元1010用于根据冗余配置请求消息向UDM发送修改签约数据请求；收发单元1020用于接收来自应用功能实体AF的冗余配置请求消息，该冗余配置请求消息包括第一指示信息或第二指示信息，其中，第一指示信息用于指示添加至少两个终端设备的第一冗余配置信息，第二指示信息用于指示删除第二冗余配置信息。
有关上述处理单元1010和收发单元1020更详细的描述可以直接参考图4至图9所示的方法实施例中相关描述直接得到，这里不加赘述。
图11为本申请实施例提供的另一种可能的通信装置的结构示意图。如图11所示，通信装置1100包括处理器1110和接口电路1120。处理器1110和接口电路1120之间相互耦合。可以理解的是，接口电路1120可以为收发器或输入输出接口。可选的，通信装置 1100还可以包括存储器1130，用于存储处理器1110执行的指令或存储处理器1110运行指令所需要的输入数据或存储处理器1110运行指令后产生的数据。
当通信装置1100用于实现图4至图9所示的方法时，处理器1110用于实现上述处理单元1010的功能，接口电路1120用于实现上述收发单元1020的功能。
可以理解的是，本申请的实施例中的处理器可以是中央处理单元(Central Processing Unit，CPU)，还可以是其它通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现场可编程门阵列(Field Programmable Gate Array，FPGA)或者其它可编程逻辑器件、晶体管逻辑器件，硬件部件或者其任意组合。通用处理器可以是微处理器，也可以是任何常规的处理器。
本申请的实施例中处理器可以是随机存取存储器(Random Access Memory，RAM)、闪存、只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)、寄存器、硬盘、移动硬盘、CD-ROM或者本领域熟知的任何其它形式的存储介质中。一种示例性的存储介质耦合至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息。当然，存储介质也可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。另外，该ASIC可以位于网络设备或终端设备中。当然，处理器和存储介质也可以作为分立组件存在于网络设备或终端设备中。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机程序或指令。在计算机上加载和执行所述计算机程序或指令时，全部或部分地执行本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、网络设备、终端设备、或者其它可编程装置。所述计算机程序或指令可以存储在计算机可读存储介质中，或者通过所述计算机可读存储介质进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是集成一个或多个可用介质的服务器等数据存储设备。所述可用介质可以是磁性介质，例如，软盘、硬盘、磁带；也可以是光介质，例如，DVD；还可以是半导体介质，例如，固态硬盘(solid state disk，SSD)。
在本申请的各个实施例中，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
可以理解的是，在本申请的实施例中涉及的各种数字编号仅为描述方便进行的区分，并不用来限制本申请的实施例的范围。上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定。

Claims (29)

  1. 一种通信的方法，其特征在于，包括：
    会话管理功能网元SMF接收来自第一终端设备的第一协议数据单元PDU会话请求，和第二终端设备的第二PDU会话请求，其中，所述第一PDU会话请求和所述第二PDU会话请求携带相同的冗余传输配置信息；
    所述SMF向用户面功能实体UPF发送创建第一PDU会话上下文请求和创建第二PDU会话上下文请求，所述创建第一PDU会话上下文请求和所述创建第二PDU会话上下文请求携带所述冗余传输配置信息；
    所述SMF接收来自所述UPF的第一响应消息和第二响应消息，所述第一响应消息携带所述第一终端设备的PDU会话标识，所述第二响应消息携带所述第二终端设备的PDU会话标识。
  2. 根据权利要求1所述的方法，其特征在于，在所述SMF向用户面功能实体UPF发送创建第一PDU会话上下文请求和创建第二PDU会话上下文请求之前，所述方法还包括：
    所述SMF向所述UPF发送第一请求消息，所述第一请求消息用于请求为所述第一终端设备和所述第二终端设备创建冗余传输上下文；
    所述SMF接收来自所述UPF的所述第一请求的响应消息，所述第一请求的响应消息包括冗余传输上下文标识，
    其中，所述创建第一PDU会话上下文请求和所述创建第二PDU会话上下文请求还携带所述冗余传输上下文标识。
  3. 根据权利要求2所述的方法，其特征在于，
    所述SMF向所述UPF发送所述第一终端设备的第一修改请求和所述第二终端设备的第二修改请求，所述第一修改请求消息携带所述第一终端设备的PDU会话标识，所述第二修改请求携带所述第二终端设备的PDU会话标识，所述第一修改请求用于指示将所述第一终端设备的PDU会话标识添加到所述冗余传输上下文中，所述第二修改请求用于指示将所述第二终端设备的PDU会话标识添加到所述冗余传输上下文中。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，
    所述冗余传输配置信息包括：冗余指示信息、冗余类型以及冗余标识，所述冗余指示信息用于指示开启冗余传输。
  5. 根据权利要求4所述的方法，其特征在于，
    所述冗余类型以及所述冗余标识是通过用户设置的。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：
    所述SMF向所述UPF发送第一删除消息和第二删除消息，所述第一删除消息用于指示删除PUD会话上下文，所述第二删除消息用于指示删除所述冗余传输上下文中的用户签约标识和/或删除所述冗余传输上下文。
  7. 一种通信的方法，其特征在于，包括：
    会话管理功能网元SMF接收来自第一终端设备的第一PDU会话请求，和第二终端设 备的第二PDU会话请求；
    所述SMF根据所述第一PDU会话请求向统一数据管理UDM获取所述第一终端设备的第一冗余传输配置信息，以及，所述SMF根据所述第二PDU会话请求向所述UDM获取所述第二终端设备的第二冗余传输配置信息；
    所述SMF向用户面功能实体UPF发送创建第一PDU会话上下文请求和创建第二PDU会话上下文请求，所述创建第一PDU会话上下文请求携带所述第一冗余传输配置信息，所述创建第二PDU会话上下文请求携带所述第二冗余传输配置信息；
    所述SMF接收来自所述UPF的第一响应消息和第二响应消息，所述第一响应消息携带所述第一终端设备的PDU会话标识，所述第二响应消息携带所述第二终端设备的PDU会话标识。
  8. 根据权利要求7所述的方法，在所述SMF向用户面功能实体UPF发送创建第一PDU会话上下文请求和创建第二PDU会话上下文请求之前，所述方法还包括：
    所述SMF向所述UPF发送第一请求消息，所述第一请求消息用于请求为所述第一终端设备和所述第二终端设备创建冗余传输上下文；
    所述SMF接收来自所述UPF的所述第一请求的响应消息，所述第一请求的响应消息包括冗余传输上下文标识，
    其中，所述创建第一PDU会话上下文请求和所述创建第二PDU会话上下文请求还携带所述冗余传输上下文标识。
  9. 根据权利要求8所述的方法，其特征在于，
    所述SMF向所述UPF发送所述第一终端设备的第一修改请求和所述第二终端设备的第二修改请求，所述第一修改请求消息携带所述第一终端设备的PDU会话标识，所述第二修改请求携带所述第二终端设备的PDU会话标识，所述第一修改请求用于指示将所述第一终端设备的PDU会话标识添加到所述冗余传输上下文中，所述第二修改请求用于指示将所述第二终端设备的PDU会话标识添加到所述冗余传输上下文中。
  10. 根据权利要求7至9中任一项所述的方法，其特征在于，
    所述第一冗余传输配置信息包括：冗余类型、冗余标识以及所述第一终端的签约冗余指示信息，所述第二冗余传输配置信息包括：所述冗余类型、所述冗余标识以及所述第二终端的签约冗余指示信息。
  11. 根据权利要求10所述的方法，其特征在于，
    所述冗余类型以及所述冗余标识是通过应用功能网元AF设置的。
  12. 根据权利要求7至11中任一项所述的方法，其特征在于，所述方法还包括：
    所述SMF向所述UPF发送第一删除消息和第二删除消息，所述第一删除消息用于指示删除PUD会话上下文，所述第二删除消息用于指示删除所述冗余传输上下文中的用户签约标识和/或删除所述冗余传输上下文。
  13. 一种通信的方法，其特征在于，包括：
    接入与移动性管理功能网元AMF接收来自第一终端设备的第一PDU会话请求，和第二终端设备的第二PDU会话请求，其中，所述第一PDU会话请求和所述第二PDU会话请求携带相同的冗余传输配置信息；
    所述AMF根据所述冗余传输配置信息为所述第一终端设备和所述第二终端设备确定 相同的会话管理功能网元SMF；
    所述AMF向所述SMF发送所述第一PDU会话请求和所述第二PDU会话请求。
  14. 根据权利要求13所述的方法，其特征在于，
    所述冗余传输配置信息包括：冗余指示信息、冗余类型以及冗余标识，所述冗余指示信息用于指示开启冗余传输，
    其中，所述AMF根据所述冗余传输配置信息为所述第一终端设备和所述第二终端设备确定相同的SMF，包括：
    所述AMF根据所述冗余标识为所述第一终端设备和所述第二终端设备确定相同的SMF。
  15. 一种通信的方法，其特征在于，包括：
    接入与移动性管理功能网元AMF接收来自第一终端设备的第一PDU会话请求，和第二终端设备的第二PDU会话请求；
    所述AMF根据所述第一PDU会话请求向统一数据管理UDM获取所述第一终端设备的第一冗余传输配置信息，以及，所述AMF根据所述第二PDU会话请求向所述UDM获取所述第二终端设备的第二冗余传输配置信息；
    所述AMF根据所述第一冗余传输配置信息和所述第二冗余传输配置信息为所述第一终端设备和所述第二终端设备确定相同的会话管理功能网元SMF；
    所述AMF向所述SMF发送所述第一PDU会话请求和所述第二PDU会话请求。
  16. 根据权利要求15所述的方法，其特征在于，
    所述第一冗余传输配置信息包括：冗余类型、冗余标识以及所述第一终端的签约冗余指示信息、所述第二冗余传输配置信息包括：所述冗余类型、所述冗余标识以及所述第二终端的签约冗余指示信息，
    其中，所述AMF根据所述第一冗余传输配置信息和所述第二冗余传输配置信息为所述第一终端设备和所述第二终端设备确定相同的SMF，包括：
    所述AMF根据所述冗余标识为所述第一终端设备和所述第二终端设备确定相同的SMF。
  17. 一种通信的方法，其特征在于，包括：
    应用功能实体AF获取第一配置信息；
    所述AF基于所述第一配置信息向网络开放功能实体NEF发送冗余配置请求消息，所述冗余配置请求消息包括第一指示信息或第二指示信息，所述第一指示信息用于指示所述NEF添加第一冗余配置信息，所述第二指示信息用于指示所述NEF删除第二冗余配置信息。
  18. 根据权利要求17所述的方法，其特征在于，所述AF基于所述第一配置信息向网络开放功能实体NEF发送冗余配置请求消息，包括：
    所述AF确定第一终端设备和所述第一终端设备的签约用户为首次绑定，以及第二终端设备与和所述第二终端设备的签约用户为首次绑定；
    所述AF向所述NEF发送冗余配置请求消息，所述冗余配置请求消息包括第一指示信息，所述第一冗余配置信息包括：所述第一终端设备的用户签约标识、所述第二终端的用户签约标识、冗余指示信息、冗余类型以及冗余标识，所述冗余指示信息用于指示开启冗 余传输。
  19. 根据权利要求17所述的方法，其特征在于，所述AF基于所述第一配置信息向网络开放功能实体NEF发送冗余配置请求消息，包括：
    所述AF确定第一终端设备和所述第一终端设备的签约用户不是首次绑定，以及第二终端设备与和所述第二终端设备的签约用户不是首次绑定；
    所述AF向所述NEF发送冗余配置请求消息，包括第二指示信息，所述第二冗余配置信息包括：所述第一终端设备的用户签约标识、所述第二终端设备的用户签约标识、以及冗余标识。
  20. 根据权利要求17至19中任一项所述的方法，其特征在于，
    所述第一配置信息包括冗余类型、所述第一终端设备的设备标识、所述第一终端设备的签约用户标识、所述第二终端设备的设备标识、所述第二终端设备的签约用户标识。
  21. 一种通信的方法，其特征在于，包括：
    网络开放功能实体NEF接收来自应用功能实体AF的冗余配置请求消息，所述冗余配置请求消息包括第一指示信息或第二指示信息，其中，所述第一指示信息用于指示添加至少两个终端设备的第一冗余配置信息，所述第二指示信息用于指示删除第二冗余配置信息；
    所述NEF根据所述冗余配置请求消息向统一数据管理UDM发送修改签约数据请求。
  22. 根据权利要求21所述的方法，其特征在于，
    第一终端设备和所述第一终端设备的签约用户为首次绑定，以及第二终端设备与和所述第二终端设备的签约用户为首次绑定时，所述冗余配置请求消息包括第一指示信息，
    所述NEF根据所述冗余配置请求消息向统一数据管理UDM发送修改签约数据请求，包括：
    所述NEF根据所述第一指示信息向所述UDM发送修改签约数据请求，所述修改签约数据请求用于指示所述UDM添加第一冗余配置信息。
  23. 根据权利要求22所述的方法，其特征在于，
    所述第一冗余配置信息包括：所述第一终端设备的用户签约标识、所述第二终端的用户签约标识、冗余指示信息、冗余类型以及冗余标识，所述冗余指示信息用于指示开启冗余传输。
  24. 根据权利要求21所述的方法，其特征在于，
    当第一终端设备和所述第一终端设备的签约用户不是首次绑定，以及第二终端设备与和所述第二终端设备的签约用户不是首次绑定时，所述冗余配置请求消息包括第二指示信息，
    所述NEF根据所述冗余配置请求消息向统一数据管理UDM发送修改签约数据请求，包括：
    所述NEF根据所述第二指示信息向所述UDM发送修改签约数据请求，所述修改签约数据请求用于指示所述UDM删除第二冗余配置信息。
  25. 根据权利要求23所述的方法，其特征在于，
    所述第二冗余配置信息包括：所述第一终端设备的用户签约标识、所述第二终端设备的用户签约标识、以及冗余标识。
  26. 一种通信装置，其特征在于，包括：
    用于执行如权利要求1至6中任一项所述方法的模块，
    或用于执行如权利要求7至12中任一项所述方法的模块，
    或用于执行如权利要求13或14所述方法的模块，
    或用于执行如权利要求15或16所述方法的模块，
    或用于执行如权利要求17至20中任一项所述方法的模块，
    或用于执行如权利要求21至25中任一项所述方法的模块。
  27. 一种通信装置，其特征在于，包括处理器和存储器，所述处理器和所述存储器耦合，所述处理器用于控制所述装置实现如权利要求1至6中任一项所述的方法，
    或控制所述装置实现如权利要求7至12中任一项所述的方法，
    或控制所述装置实现如权利要求13或14所述的方法，
    或控制所述装置实现如权利要求15或16所述的方法，
    或控制所述装置实现如权利要求17至20中任一项所述的方法，
    或控制所述装置实现如权利要求21至25中任一项所述的方法。
  28. 一种通信装置，其特征在于，包括处理器和接口电路，所述接口电路用于接收来自所述通信装置之外的其它通信装置的信号并传输至所述处理器或将来自所述处理器的信号发送给所述通信装置之外的其它通信装置，所述处理器通过逻辑电路或执行代码指令用于实现如权利要求1至6中任一项所述的方法，或实现如权利要求7至12中任一项所述的方法，或实现如权利要求13或14所述的方法，或实现如权利要求15或16所述的方法，或实现如权利要求17至20中任一项所述的方法，或实现如权利要求21至25中任一项所述的方法。
  29. 一种计算机可读存储介质，其特征在于，所述存储介质中存储有计算机程序或指令，当所述计算机程序或指令被通信装置执行时，实现如权利要求1至6中任一项所述的方法，或实现如权利要求7至12中任一项所述的方法，或实现如权利要求13或14所述的方法，或实现如权利要求15或16所述的方法，或实现如权利要求17至20中任一项所述的方法，或实现如权利要求21至25中任一项所述的方法。
PCT/CN2022/117164 2021-11-05 2022-09-06 一种通信的方法和装置 WO2023077948A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111307021.4A CN116095667A (zh) 2021-11-05 2021-11-05 一种通信的方法和装置
CN202111307021.4 2021-11-05

Publications (1)

Publication Number Publication Date
WO2023077948A1 true WO2023077948A1 (zh) 2023-05-11

Family

ID=86212521

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/117164 WO2023077948A1 (zh) 2021-11-05 2022-09-06 一种通信的方法和装置

Country Status (2)

Country Link
CN (1) CN116095667A (zh)
WO (1) WO2023077948A1 (zh)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111492608A (zh) * 2018-11-28 2020-08-04 Oppo广东移动通信有限公司 一种数据传输方法及装置、终端
CN111917806A (zh) * 2019-05-07 2020-11-10 华为技术有限公司 通信方法及装置
US20210051733A1 (en) * 2019-08-16 2021-02-18 Lg Electronics Inc. Method and apparatus for performing rach procedure by ue in wireless communication system
WO2021063383A1 (en) * 2019-10-04 2021-04-08 Huawei Technologies Co., Ltd. Support group communications with shared downlink data
CN112788680A (zh) * 2019-11-07 2021-05-11 华为技术有限公司 一种数据传输的方法及相关设备
WO2021093062A1 (en) * 2019-12-06 2021-05-20 Zte Corporation Session management function registration and deregistration
CN113543219A (zh) * 2020-04-13 2021-10-22 华为技术有限公司 通信方法和装置

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111492608A (zh) * 2018-11-28 2020-08-04 Oppo广东移动通信有限公司 一种数据传输方法及装置、终端
CN111917806A (zh) * 2019-05-07 2020-11-10 华为技术有限公司 通信方法及装置
US20210051733A1 (en) * 2019-08-16 2021-02-18 Lg Electronics Inc. Method and apparatus for performing rach procedure by ue in wireless communication system
WO2021063383A1 (en) * 2019-10-04 2021-04-08 Huawei Technologies Co., Ltd. Support group communications with shared downlink data
CN112788680A (zh) * 2019-11-07 2021-05-11 华为技术有限公司 一种数据传输的方法及相关设备
WO2021093062A1 (en) * 2019-12-06 2021-05-20 Zte Corporation Session management function registration and deregistration
CN113543219A (zh) * 2020-04-13 2021-10-22 华为技术有限公司 通信方法和装置

Also Published As

Publication number Publication date
CN116095667A (zh) 2023-05-09

Similar Documents

Publication Publication Date Title
US11917498B2 (en) Communication method and communications apparatus
CN108323245B (zh) 一种注册及会话建立的方法、终端和amf实体
CN110121897B (zh) 一种会话建立的方法及设备
US11805394B2 (en) Context management method and apparatus
CN112566149B (zh) 配置业务的方法、通信装置和通信系统
WO2022152238A1 (zh) 一种通信方法及通信装置
US20210045033A1 (en) Communication Method And Communications Apparatus
CN111835802B (zh) 一种通信方法及装置
WO2021083321A1 (zh) 一种通信方法及设备
WO2021212939A1 (zh) 通信方法、装置及系统
WO2022032597A1 (zh) 一种网络能力开放的方法、装置及系统
JP2021513825A (ja) Ｓｓｃモードを決定するための方法および装置
WO2022052875A1 (zh) 终端跨区域通信方法、网元设备及存储介质
CN112672336B (zh) 实现外部认证的方法、通信装置及通信系统
WO2021227600A1 (zh) 一种网络切片控制方法及通信装置
JP7367186B2 (ja) ページング方法と機器
WO2023077948A1 (zh) 一种通信的方法和装置
KR20240024286A (ko) 온보딩을 수행하는 방법 및 장치
WO2021042381A1 (zh) 一种通信方法、装置及系统
WO2024061205A1 (zh) 参数获取方法、装置、第一网络功能及第二网络功能
WO2024051313A1 (zh) 通信资源管理方法、装置、系统及存储介质
WO2023020046A1 (zh) 一种通信方法及通信装置
WO2023143212A1 (zh) 一种通信方法及装置
EP4369788A1 (en) Communication tunnel management method, apparatus and system
WO2021168862A1 (zh) 一种通信方法及设备

Legal Events

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

Ref document number: 22888979

Country of ref document: EP

Kind code of ref document: A1