WO2022032543A1 - 一种通信方法及装置 - Google Patents

一种通信方法及装置 Download PDF

Info

Publication number
WO2022032543A1
WO2022032543A1 PCT/CN2020/108743 CN2020108743W WO2022032543A1 WO 2022032543 A1 WO2022032543 A1 WO 2022032543A1 CN 2020108743 W CN2020108743 W CN 2020108743W WO 2022032543 A1 WO2022032543 A1 WO 2022032543A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
accounting
quality
service flow
bearer
Prior art date
Application number
PCT/CN2020/108743
Other languages
English (en)
French (fr)
Inventor
周晓云
李文强
徐要强
宗在峰
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20949042.4A priority Critical patent/EP4191950A4/en
Priority to PCT/CN2020/108743 priority patent/WO2022032543A1/zh
Priority to CN202080104172.7A priority patent/CN116097622A/zh
Publication of WO2022032543A1 publication Critical patent/WO2022032543A1/zh
Priority to US18/167,460 priority patent/US20230188957A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/49—Connection to several service providers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8016—Rating or billing plans; Tariff determination aspects based on quality of service [QoS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/80—Rating or billing plans; Tariff determination aspects
    • H04M15/8038—Roaming or handoff
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/82—Criteria or parameters used for performing billing operations
    • H04M15/8228—Session based
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/14—Reselecting a network or an air interface

Definitions

  • the present application relates to the field of wireless communication technologies, and in particular, to a communication method and apparatus.
  • a mobile cellular network functions such as charging can be implemented by allocating an accounting session to a terminal device.
  • the session management function (SMF) network element allocates accounting sessions according to the session granularity of the protocol data unit (PDU), that is, for different PDUs Sessions are assigned different accounting sessions.
  • PDU protocol data unit
  • EPS evolved packet system
  • the SMF can allocate different accounting sessions for different EPS bearers (bearers).
  • SMF network elements allocate accounting sessions according to different granularities, when the terminal device switches from 5GS to EPS, or from EPS to 5GS, how to update the accounting session is an urgent problem to be solved. The problem.
  • the purpose of the embodiments of the present application is to provide a communication method and apparatus to solve the problem of how to update the accounting session when a terminal device switches between different mobile cellular networks.
  • an embodiment of the present application provides a communication method, including: after a session management function network element establishes a protocol data unit session including a first quality of service flow for a terminal device in a first network, it can send a first message to the authentication
  • the authorization accounting server indicates the identifier of the first accounting session corresponding to the first quality of service flow; when the terminal device switches from the first network to the second network, if the session management function network element determines to map the first quality of service flow to the The first bearer in the second network can send a second message including the identifier of the first accounting session corresponding to the first quality of service flow and the information of the first bearer to the authentication, authorization and accounting server, so that the second message can be used for to instruct the authentication-authorized accounting server to update the first accounting session.
  • the session management function network element instructs the authentication, authorization and accounting server to update the first accounting session according to the information of the first bearer, thereby realizing the switching to the second network.
  • the terminal device controls the service access transmitted through the first bearer, such as access control, charging and service provision.
  • the protocol data unit session further includes a second quality of service flow
  • the session management function network element may indicate the second quality of service flow corresponding to the second quality of service flow to the authentication, authorization and accounting server through a third message.
  • the identification of the accounting session when the terminal device switches from the first network to the second network, if the session management function network element determines to map the second quality of service flow to the first bearer, it can authorize the authentication
  • the billing server sends a fourth message, wherein the fourth message includes the identifier of the second billing session corresponding to the second quality of service flow and the information of the first bearer, and the fourth message is used to indicate the
  • the authentication-authorized accounting server updates the second accounting session.
  • the session management function network element instructs the AAA server to update the second accounting session according to the information of the first bearer, so that after switching to the second network, According to the information of the second accounting session, the service access transmitted by the terminal device through the first bearer is controlled, such as access control, charging and service provision.
  • the method further includes: the session management function network element receives a disconnection from the authentication, authorization and accounting server.
  • a connection request message, the disconnection request message includes the identifier of the first accounting session, and the disconnection request message is used to request deletion of the resource corresponding to the first quality of service flow; the session management function network The element sends an update bearer request to the serving gateway, where the update bearer request is used to request to delete the resource corresponding to the first quality of service flow.
  • the protocol data unit session further includes a third quality of service flow; the method further includes: the session management function network element maps the third quality of service flow of the terminal device to the first bearer; the session management function network element sends the first stop indication information and the identifier of the third accounting session corresponding to the third quality of service flow to the authentication, authorization and accounting server, and the first stop The indication information is used to instruct the authentication, authorization and accounting server to stop the third accounting session.
  • the protocol data unit session further includes a fourth quality of service flow
  • the method further includes: the session management function network element sends a fifth message to the authentication, authorization and accounting server, the The fifth message includes the identifier of the fourth accounting session corresponding to the fourth quality of service flow; the session management function network element determines that the terminal device is switched from the first network to the second network after determining that the fourth quality of service flow is not mapped to the bearer in the second network; the session management function network element sends the second stop indication information and the first stop instruction corresponding to the fourth quality of service flow to the authentication, authorization and accounting server. 4.
  • the identifier of the accounting session, and the second stop indication information is used to instruct the authentication and authorization accounting server to stop the fourth accounting session.
  • the fourth accounting session corresponding to the fourth quality of service flow can be stopped to avoid managing too many redundant accounting sessions, thereby improving accounting Session management efficiency.
  • the identifier of the first accounting session includes a first charging identifier, the address of the network element of the session management function, and the identifier information of the first quality of service flow, and the first accounting
  • the charging identifier is the charging identifier allocated by the session management function network element for the protocol data unit session.
  • the identifier of the second accounting session includes a first charging identifier, an address of the session management function network element, and identifier information of the second quality of service flow.
  • the information of the first bearer includes at least one of the following: a wireless access type corresponding to the first bearer; and a quality of service document corresponding to the first bearer.
  • the information of the first bearer further includes a second charging identifier allocated by the session management function network element for the first bearer.
  • the method further includes: after the session management function network element determines that the terminal device is switched from the second network to the first network, mapping the first bearer to the a fifth quality of service flow corresponding to the first network; the session management function network element sends a sixth message to the authentication, authorization and accounting server; wherein, the sixth message includes the first accounting session and the information corresponding to the fifth quality of service flow, and the sixth message is used to instruct the authentication, authorization and accounting server to update the first accounting session.
  • the session management function network element instructs the authentication, authorization and accounting server to update the first accounting session according to the information corresponding to the fifth quality of service flow, so as to realize the switching
  • control the user's access to services transmitted through the fifth quality of service stream such as access control, charging and service provision, according to the information of the first accounting session.
  • the information corresponding to the fifth quality of service flow includes one or more of the following:
  • the wireless access type corresponding to the fifth quality of service flow The wireless access type corresponding to the fifth quality of service flow; the quality of service document corresponding to the fifth quality of service flow.
  • the information corresponding to the fifth quality of service flow further includes the first charging identifier.
  • the method further includes: after the session management function network element determines that the terminal device is switched from the second network to the first network, mapping the first bearer to the a sixth quality of service flow corresponding to the first network; the session management function network element sends a seventh message to the authentication, authorization and accounting server; wherein, the seventh message includes the second accounting session and the information corresponding to the sixth quality of service flow, the sixth message is used to instruct the authentication and authorization accounting server to update the second accounting session.
  • the present application further provides a communication device, the communication device having any of the methods provided in the above-mentioned first aspect.
  • the communication device may be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the communication apparatus includes: a processor configured to support the communication apparatus to perform the corresponding function of the session management function network element in the method shown above.
  • the communication device may also include a memory, which may be coupled to the processor, which holds program instructions and data necessary for the communication device.
  • the communication apparatus further includes a communication interface, where the communication interface is used to support communication between the communication apparatus and a device such as an authentication, authorization and accounting server.
  • the communication device includes corresponding functional units, which are respectively used to implement the steps in the above method.
  • the functions can be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more units corresponding to the above-mentioned functions.
  • the structure of the communication apparatus includes a processing unit and a communication unit, and these units can perform the corresponding functions in the above method examples.
  • these units can perform the corresponding functions in the above method examples.
  • the description of the method provided in the first aspect which is not repeated here.
  • an embodiment of the present application provides a communication method, including: a session management function network element establishes a first bearer for a terminal device in a second network; the session management function network element determines that the terminal device is from the first bearer. After the second network is switched to the first network, the first bearer is mapped to the fifth quality of service flow corresponding to the first network; the session management function network element reports to the authentication, authorization and accounting server Sending a sixth message; wherein the sixth message includes the identifier of the first accounting session and the information corresponding to the fifth quality of service flow, and the sixth message is used to instruct the authentication, authorization and accounting server to update the first billing session.
  • the session management function network element instructs the authentication, authorization and accounting server to update the first accounting session according to the information corresponding to the fifth quality of service flow, so as to realize the switching
  • control the service access of the terminal device through the fifth quality of service flow such as access control, charging and service provision, according to the information of the first accounting session.
  • the information corresponding to the fifth quality of service flow includes one or more of the following:
  • the wireless access type corresponding to the fifth quality of service flow The wireless access type corresponding to the fifth quality of service flow; the quality of service document corresponding to the fifth quality of service flow.
  • the information corresponding to the fifth quality of service flow further includes the first charging identifier.
  • the method further includes: after the session management function network element determines that the terminal device is switched from the second network to the first network, mapping the first bearer to the a sixth quality of service flow corresponding to the first network; the session management function network element sends a seventh message to the authentication, authorization and accounting server; wherein, the seventh message includes the second accounting session and the information corresponding to the sixth quality of service flow, the sixth message is used to instruct the authentication and authorization accounting server to update the second accounting session.
  • the present application further provides a communication device, the communication device having any of the methods provided in the third aspect above.
  • the communication device may be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more units or modules corresponding to the above functions.
  • the communication apparatus includes: a processor configured to support the communication apparatus to perform the corresponding function of the session management function network element in the method shown above.
  • the communication device may also include a memory, which may be coupled to the processor, which holds program instructions and data necessary for the communication device.
  • the communication apparatus further includes a communication interface, where the communication interface is used to support communication between the communication apparatus and a device such as an authentication, authorization and accounting server.
  • the communication device includes corresponding functional units, which are respectively used to implement the steps in the above method.
  • the functions can be implemented by hardware, or by executing corresponding software by hardware.
  • the hardware or software includes one or more units corresponding to the above-mentioned functions.
  • the structure of the communication apparatus includes a processing unit and a communication unit, and these units can perform the corresponding functions in the above method examples.
  • these units can perform the corresponding functions in the above method examples.
  • the present application provides a chip, comprising a processor, which is coupled to a memory and configured to execute a computer program or instruction stored in the memory, when the processor executes the computer program or instruction , so that the first aspect to or the method in any possible implementation manner of the first aspect is implemented, or the third aspect to or the method in any possible implementation manner of the third aspect is implemented.
  • the present application provides a communication apparatus, the communication apparatus includes a processor, when the processor executes a computer program or an instruction in a memory, as in the first aspect or any possible implementation manner of the first aspect The method in is performed, or as in the third aspect or any of the possible implementations of the third aspect is performed.
  • the present application provides a communication device, the communication device includes a processor and a memory, the memory is used for storing computer programs or instructions; the processor is used for executing the computer programs or instructions stored in the memory, to cause the communication device to perform the method as in the first aspect or any one of the possible implementations of the first aspect, or to cause the communication device to perform as in the third aspect or any of the possible implementations of the third aspect Methods.
  • the present application provides a communication device, the communication device includes a processor, a memory and a transceiver, the transceiver is used to receive a signal or send a signal; the memory is used to store a computer program or instruction; the processor, for invoking the computer program or instructions from the memory to execute the method in the first aspect or any possible implementation manner of the first aspect; or, the processor, for executing the method from the memory
  • the memory invokes the computer program or instructions to perform the method as in the third aspect or any of the possible implementations of the third aspect.
  • a computer-readable storage medium for storing a computer program, the computer program comprising instructions for executing the method in the first aspect or any possible implementation manner of the first aspect, or the computer
  • the program includes instructions for carrying out the method of the third aspect or any of the possible implementations of the third aspect.
  • a computer program product comprising: computer program code, when the computer program code is run on a computer, causing the computer to execute the first aspect or any one of the first aspects The method in the possible implementation manner, or causing the computer to execute the third aspect or the method in any one of the possible implementation manners of the third aspect.
  • FIG. 1 is a schematic diagram of a network architecture suitable for an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of establishing a PDU session in 5GS provided by an embodiment of the present application
  • FIG. 4 is a schematic diagram of accounting session update when switching from 5GS to EPS according to an embodiment of the present application
  • FIG. 5 is a schematic diagram of accounting session update when switching from EPS to 5GS according to an embodiment of the present application
  • FIG. 6 is a schematic diagram of accounting session update when switching from 5GS to EPS according to an embodiment of the present application
  • FIG. 7 is a schematic diagram of establishing an accounting session for a bearer in an EPS according to an embodiment of the present application.
  • FIG. 8 is a schematic diagram of accounting session update when switching from EPS to 5GS provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • 5GS includes but is not limited to new radio (NR) system
  • EPS includes but is not limited to long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division dual labor (time division duplex, TDD), etc., are not limited here.
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD time division duplex
  • FIG. 1 it is a schematic diagram of a network architecture applicable to the embodiment of the present application.
  • the authentication authorization and accounting (AAA) server located in the data network (data network) can monitor the terminal device.
  • the AAA server can support remote user dial-in authentication (remote authentication dial in user service, RADIUS) and Diameter protocol.
  • RADIUS remote authentication dial in user service
  • the network shown in Figure 1 also includes an access and mobility management function (AMF) network element, an SMF network element, and a user plane function (UPF), etc.
  • AMF access and mobility management function
  • SMF SMF network element
  • UPF user plane function
  • SMF network elements allocate different accounting sessions for different PDU sessions.
  • Each accounting session corresponds to an accounting session identity (acct-session-ID) or session-ID (session-ID).
  • the identity corresponding to the accounting session is acct-session-ID;
  • the identification corresponding to the accounting session is (session-ID), and the accounting session identification or session identification is used to globally uniquely identify an accounting session.
  • the billing session identifier includes information such as a charging identifier (charging ID) and the address of the SMF network element.
  • the address of the SMF network element may be the billing address of the SMF network element, and may specifically refer to information such as an internet protocol (internet protocol, IP) address of the SMF network element.
  • the identifier corresponding to the accounting session is acct-session-ID as an example for description.
  • the identifier corresponding to the accounting session may also be session-ID, and the difference lies in the The value is dynamically allocated by the session management function network element and remains globally unique.
  • the SMF network element assigns a charging identifier to the PDU session
  • the charging identifiers in the accounting session identifiers corresponding to multiple quality of service (QoS) flows in the PDU session are the same That is, the accounting session identifiers corresponding to multiple QoS flows in the PDU session are the same, and the accounting session identifiers of the PDU session cannot identify different QoS flows in the PDU session.
  • QoS quality of service
  • the PDU session in 5GS is called a packet data network (PDN) connection in EPS.
  • PDN packet data network
  • SMF network elements can allocate different bearers to different bearers.
  • each bearer in the PDN connection has a different accounting session identifier.
  • the terminal device may be a device with a wireless transceiver function or a chip that can be installed in any device, and may also be referred to as user equipment (user equipment, UE), an access terminal, a subscriber unit, or a subscriber station. , mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent or user equipment.
  • user equipment user equipment
  • UE user equipment
  • access terminal a subscriber unit
  • subscriber station mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent or user equipment.
  • the terminal device in this embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, an industrial Wireless terminal in industrial control, wireless terminal in self driving, wireless terminal in remote medical, wireless terminal in smart grid, transportation safety Wireless terminals in smart cities, wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • a mobile phone mobile phone
  • a tablet computer (Pad)
  • a computer with a wireless transceiver function a virtual reality (VR) terminal, an augmented reality (AR) terminal
  • an industrial Wireless terminal in industrial control wireless terminal in self driving, wireless terminal in remote medical, wireless terminal in smart grid, transportation safety Wireless terminals in smart cities, wireless terminals in smart cities, wireless terminals in smart homes, etc.
  • the access network equipment may be a next-generation base station (generation node B, gNB) in 5GS, an evolved base station (evolutional node B, eNB) in EPS, or the like.
  • generation node B generation node B
  • eNB evolved base station
  • FIG. 2 a schematic flowchart of a communication method provided by an embodiment of the present application is shown. Referring to Figure 2, the method includes:
  • Step 201 The session management function network element establishes a PDU session for a terminal device in a first network, where the PDU session includes a first QoS flow.
  • the first network may refer to 5GS
  • the session management function network element may refer to an SMF network element, or may refer to both an SMF network element and a control plane PDN gateway (packet data network gateway for control plane, PGW-C) function network element.
  • PDN gateway packet data network gateway for control plane, PGW-C
  • the PDU session may include, in addition to the first QoS flow, a second QoS flow, a third QoS flow, a fourth QoS flow, etc., and the specific number of QoS flows included is not limited in this embodiment of the present application.
  • the QoS flow included in the PDU session can be divided into a default QoS flow and a dedicated QoS flow. limited.
  • Step 202 The session management function network element sends a first message to the AAA server, where the first message includes the identifier of the first accounting session corresponding to the first QoS flow.
  • the identifier of the first accounting session is allocated by the network element of the session management function.
  • the identifier of the first billing session may include, but is not limited to, the following information: the first charging identifier, the address of the network element of the session management function, and the identifier information of the first QoS flow.
  • the first charging identifier is a charging identifier allocated by the session management function network element for the PDU session, and may be, for example, an identifier allocated for a default QoS flow in the PDU session.
  • the address of the session management function network element may refer to the IP address of the session management function network element.
  • the identification information of the first QoS flow may refer to a QoS flow identifier (QoS flow identifier, QFI) of the first QoS flow or other information allocated by the session management function network element for identifying the first QoS flow.
  • QFI QoS flow identifier
  • a PDU session may include multiple different QoS flows, but the accounting session is allocated for the PDU session, that is to say, the prior art is for accounting for the PDU session, There is no concrete implementation of separate accounting for these QoS flows.
  • the identification information of the QoS flow is added to the accounting session identification of the PDU session, so as to allocate different accounting session identifications for different QoS flows, so as to realize Each QoS flow in a PDU session is billed separately.
  • Step 203 After determining that the terminal device switches from the first network to the second network, the session management function network element maps the first QoS flow to the first bearer corresponding to the second network.
  • the session management function network element may determine the identifier of the first bearer corresponding to the first QoS flow in the second network, and the session management function network element may send the first bearer to the second network The identifier is used to request the second network to establish the first bearer.
  • the second network may refer to EPS.
  • How the network element of the session management function specifically determines that the terminal device switches to the second network is not limited in this embodiment of the present application. For details, reference may be made to the description in the prior art, which will not be repeated here.
  • Step 204 The session management function network element sends a second message to the AAA server.
  • the second message includes the identifier of the first accounting session corresponding to the first QoS flow and the information of the first bearer, and the information of the first bearer can be used to update the identifier of the first accounting session.
  • the second message is used to instruct the AAA server to update the first accounting session.
  • the information of the first bearer includes at least one of the following:
  • the wireless access type corresponding to the first bearer the QoS profile corresponding to the first bearer; the packet filter corresponding to the first bearer; the second charging identifier allocated by the session management network element for the first bearer .
  • the session management function network element instructs the AAA server to update the first accounting session according to the information of the first bearer, so that after switching to the second network, According to the information of the first accounting session, the service access transmitted by the terminal device through the first bearer is controlled, such as access control, charging and service provision.
  • the network element with the session management function may establish a PDU session for the terminal device in the first network, and assign different QoS flows in the PDU session with different accounting session identifiers.
  • a billing session corresponding to the QoS flow can be established, and the billing session of each QoS flow can be uniquely identified by the identification of the billing session, wherein the identification of the billing session includes Identification information of the QoS flow.
  • the process shown in FIG. 3 is based on the relevant content of the PDU session establishment in the existing document TS 23.502, and the above-mentioned document may be referred to for details.
  • Step 301 The terminal device initiates a PDU session establishment process by sending a PDU session establishment request message, and the PDU session establishment request message includes information such as authentication and authorization.
  • Step 302 The AMF network element sends a PDU session establishment context request message to the session management function network element.
  • the specific name of the message is not limited, for example, it may be Nsmf_PDUSession_CreateSMContext Request, etc., and the message may include information such as authentication and authorization.
  • Step 303 The session management function network element sends a response message to the AMF network element.
  • the session management function network element needs to initiate an N4 session establishment process, and the specific process will not be repeated.
  • the network side also needs to perform processes such as authentication and authorization on the terminal device, and the specific process will not be described.
  • processes such as authentication and authorization on the terminal device, and the specific process will not be described.
  • the PDU session includes a first QoS flow, a second QoS flow, a third QoS flow and a fourth QoS flow, the following describes how to establish an accounting session corresponding to each QoS flow.
  • an accounting session corresponding to the first QoS flow may be established through the following steps.
  • Step 304 The session management function network element sends an accounting-request (accounting-request) message to the AAA server for requesting to start accounting for the first QoS flow in the PDU session.
  • accounting-request accounting-request
  • the billing request message may refer to the first message in the process of FIG. 2, and the content carried in the billing request message, which is not limited in the embodiment of the present application, may include, but is not limited to, the identification of the terminal device (or the user), The address of the terminal device, the identifier of the first accounting session corresponding to the first QoS flow (hereinafter referred to as the accounting session identifier 1), the first charging identifier (the identifier allocated by the session management function network element for the PDU session), the first The QFI of the QoS flow (hereinafter referred to as the first QFI), the radio access type (the radio access type in 5GS is next generation RAN, NG-RAN), and the packet filter of the first QoS flow ) and the QoS document corresponding to the first QoS flow.
  • the accounting session identifier 1 The address of the terminal device
  • the identifier of the first accounting session corresponding to the first QoS flow hereinafter referred to as the accounting session identifier 1
  • the accounting session identifier 1 may include the following information: the first charging identifier, the address of the session management function network element, and the identifier information of the first QoS flow.
  • the identification information of the first QoS flow may refer to the first QFI of the first QoS flow or other information allocated by the session management function network element for identifying the first QoS flow.
  • Step 305 The AAA server returns a corresponding response message.
  • the session management function network element may initiate a second QoS flow establishment process, and the specific process will not be repeated.
  • an accounting session corresponding to the second QoS flow may be established, which specifically includes the following steps.
  • Step 306 The session management function network element sends an accounting request message to the AAA server, which is used to request to start accounting for the second QoS flow in the PDU session.
  • the billing request message may have other names, for example, it may be the third message.
  • the content carried in the accounting request message is not limited in the embodiments of the present application, and may include but not limited to the identifier of the terminal device, the address of the terminal device, and the identifier of the second accounting session corresponding to the second QoS flow (hereinafter referred to as the identifier of the second accounting session).
  • Accounting session identifier 2 may include but not limited to the identifier of the terminal device, the address of the terminal device, and the identifier of the second accounting session corresponding to the second QoS flow (hereinafter referred to as the identifier of the second accounting session).
  • QFI of the second QoS flow denotes
  • the accounting session identifier 2 may include the following information: the first charging identifier, the address of the session management function network element, and the identifier information of the second QoS flow.
  • the identification information of the second QoS flow may refer to the second QFI of the second QoS flow or other information allocated by the session management function network element for identifying the second QoS flow.
  • Step 307 The AAA server returns a corresponding response message.
  • the session management function network element decides to create the third QoS flow and the fourth QoS flow in the PDU session, the same method as above can be used to establish the identifier of the third accounting session corresponding to the third QoS flow, and the fourth The identifier of the fourth accounting session corresponding to the QoS flow, and the specific process will not be repeated.
  • the identifier of the third accounting session may include the following information: the first charging identifier, the address of the network element of the session management function, and the identifier information of the third QoS flow.
  • the identification information of the third QoS flow may refer to the third QFI of the third QoS flow or other information allocated by the session management function network element for identifying the third QoS flow.
  • the identification of the fourth accounting session may include the following information: the first charging identification, the address of the network element of the session management function, and the identification information of the fourth QoS flow.
  • the identification information of the fourth QoS flow may refer to the fourth QFI of the fourth QoS flow or other information allocated by the session management function network element for identifying the fourth QoS flow.
  • the session management function network element can update the accounting session corresponding to each QoS flow according to the bearer corresponding to each QoS flow. If there are multiple QoS flows mapped to the same bearer, the session management function network element updates the information corresponding to the bearer for each accounting session, which will be described in detail below with reference to FIG. 4 .
  • Step 401 The terminal device switches from 5GS to EPS.
  • the session management function network element determines to map the first QoS flow and the second QoS flow in the PDU session to the first bearer.
  • the network element of the session management function specifically determines to map the first QoS flow and the second QoS flow to the first bearer is not limited in this embodiment of the present application.
  • Step 402 The session management function network element sends a first accounting request message to the AAA server.
  • the first billing request message may refer to the second message in the process of FIG. 2 .
  • the first billing request message includes the identifier of the first billing session corresponding to the first QoS flow and the information of the first bearer, the information of the first bearer is used to update the first billing session, and the first billing request message is used to instructing the AAA server to update the first accounting session corresponding to the first QoS flow.
  • the information of the first bearer includes at least one of the following:
  • the radio access type corresponding to the first bearer for example, in EPS, the radio access type of the first bearer may refer to an evolved universal terrestrial radio access network (Evolved Universal Terrestrial Radio Access Network, E-UTRAN); A packet filter corresponding to the first bearer; and a QoS document corresponding to the first bearer.
  • E-UTRAN evolved Universal Terrestrial Radio Access Network
  • the session management network element allocates the second charging identifier to the first bearer
  • the information of the first bearer further includes the second charging identifier
  • Step 403 The AAA server updates the first accounting session and returns a response message.
  • the AAA server may update the first accounting identifier in the first accounting session to the second accounting identifier, etc., so as to update the first accounting session.
  • Step 404 The session management function network element sends a second accounting request message to the AAA server.
  • the second accounting request message may have other names, for example, may be the fourth message.
  • the second accounting request message includes the identifier of the second accounting session corresponding to the second QoS flow and the information of the first bearer, where the information of the first bearer is used to update the second accounting session, and the second accounting request message uses instructing the AAA server to update the second accounting session corresponding to the second QoS flow.
  • the session management network element allocates the second charging identifier to the first bearer
  • the information of the first bearer further includes the second charging identifier
  • Step 405 The AAA server updates the second accounting session and returns a response message.
  • the AAA server may update the first accounting identifier in the second accounting session to the second accounting identifier, etc., so as to update the first accounting session.
  • step 403 and step 405 after the two steps of step 403 and step 405, after the AAA server updates the second billing session, it will perform billing according to the first bearer, that is, only the first bearer will be billed for both QoS flows. Billing is no longer based on QoS flows. Although the first QoS flow and the second QoS flow are mapped to the first bearer, the session management function network element still maintains the packet filter corresponding to each QoS flow.
  • the AAA server determines to delete the resource corresponding to the first QoS flow, the following steps may be further included.
  • Step 406 The AAA server sends a disconnection request message to the session management network element, where the disconnection request message includes the identifier of the first accounting session, and the disconnection request message is used to request deletion of the first accounting session.
  • Step 407 The session management network element sends an update bearer request to the serving gateway, where the update bearer request is used to request deletion of the resource corresponding to the first QoS flow, and the update bearer request may include the identifier of the first bearer.
  • the serving gateway may delete resources such as a packet filter corresponding to the first QoS flow from the packet filter of the first bearer.
  • Step 408 The network side interacts with the terminal device to complete the update process of the first bearer, and the specific process will not be repeated.
  • the AAA server determines to delete the resource corresponding to the second QoS flow, the following steps may be further included.
  • Step 409 The AAA server sends a disconnection request message to the session management network element, where the disconnection request message includes the identifier of the second accounting session, and the disconnection request message is used to request deletion of the second accounting session.
  • the session management network element determines that the second QoS flow corresponding to the first bearer is deleted, and there is no corresponding QoS flow for the first bearer, the following steps may be performed.
  • Step 410 The session management network element sends a bearer deletion request to the serving gateway, where the bearer deletion request is used to request deletion of the resource corresponding to the second QoS flow, and the bearer deletion request may include the identifier of the first bearer.
  • the serving gateway may delete resources such as a packet filter corresponding to the second QoS flow from the packet filter of the first bearer.
  • Step 411 The network side interacts with the terminal device to complete the process of deleting the first bearer, that is, the process of deactivating the first bearer, and the specific process will not be repeated.
  • the session management function network element determines to map the first bearer to the fifth QoS process and the sixth QoS process.
  • the specific steps are as shown in the figure 5 shows:
  • Step 501 The session management function network element determines to map the first bearer to the fifth QoS flow corresponding to the first network, and sends a third accounting request message to the AAA server.
  • the network element of the session management function specifically determines to map the first bearer to the fifth QoS flow is not limited in this embodiment of the present application.
  • the third accounting request message includes the identifier of the first accounting session and information corresponding to the fifth QoS flow, and the third accounting request message is used to instruct the AAA server to update the first accounting session.
  • Information corresponding to the first QoS flow may be used to update the first accounting session.
  • the information corresponding to the fifth QoS flow includes one or more of the following:
  • the wireless access type corresponding to the fifth QoS flow; the packet filter corresponding to the fifth QoS flow; and the QoS document corresponding to the fifth QoS flow is the wireless access type corresponding to the fifth QoS flow.
  • the session management network element allocates the second charging identifier to the first bearer, the information corresponding to the fifth QoS flow further includes the first charging identifier.
  • Step 502 The AAA server updates the first accounting session and returns a corresponding response message.
  • Step 503 The session management function network element determines to map the first bearer to the sixth QoS flow corresponding to the first network, and sends a fourth accounting request message to the AAA server.
  • the fourth accounting request message includes the identifier of the second accounting session and information corresponding to the sixth QoS flow, and the fourth accounting request message is used to instruct the AAA server to update the second accounting account session.
  • the information corresponding to the sixth QoS flow includes one or more of the following:
  • the wireless access type corresponding to the sixth QoS flow; the packet filter corresponding to the sixth QoS flow; and the QoS document corresponding to the sixth QoS flow is the wireless access type corresponding to the sixth QoS flow.
  • the session management network element allocates the second charging identifier to the first bearer, the information corresponding to the sixth QoS flow further includes the first charging identifier.
  • Step 504 The AAA server updates the second accounting session and returns a corresponding response message.
  • the session management function network element may update the accounting session corresponding to each QoS flow according to the bearer corresponding to each QoS flow. If there are multiple QoS flows mapped to the same bearer, the session management function network element may also update one accounting session and stop other accounting sessions, which will be described in detail below with reference to FIG. 6 .
  • Step 601 The terminal device switches from 5GS to EPS.
  • the session management function network element determines to map the first QoS flow and the third QoS flow in the PDU session to the first bearer.
  • the network element of the session management function specifically determines to map the first QoS flow and the third QoS flow to the first bearer is not limited in this embodiment of the present application.
  • Step 602 The session management function network element sends a fifth accounting request message to the AAA server.
  • the fifth accounting request message may refer to the second message in the process of FIG. 2 .
  • the fifth accounting request message includes the identifier of the first accounting session corresponding to the first QoS flow and the information of the first bearer, and the information of the first bearer is used to update the first accounting session, and the fifth accounting request message is used to instructing the AAA server to update the first accounting session corresponding to the first QoS flow.
  • the fifth accounting request message may further include a packet filter aggregated by the packet filter of the first QoS flow and the packet filter of the third QoS flow.
  • Step 603 The AAA server updates the first accounting session and returns a response message.
  • the third accounting session corresponding to the third QoS flow may be stopped.
  • Step 604 The session management function network element sends a sixth accounting request message to the AAA server.
  • the sixth billing request message includes first stop indication information and an identifier of a third billing session corresponding to the third QoS flow, where the first stop indication information is used to instruct the AAA server to stop the third billing session.
  • Step 605 The AAA server deletes the information corresponding to the third accounting session, and returns a response message.
  • step 503 and step 505 after the AAA server stops the third accounting session, it controls the user's service access transmitted through the first bearer according to the information of the first accounting session, such as access control, Billing and service provision, etc.
  • the session management function network element may send the identifier of the fourth accounting session corresponding to the fourth QoS flow to the AAA server through a fifth message.
  • the session management function network element determines that the fourth QoS flow is not mapped to any bearer in the EPS network, and can instruct the AAA server to delete the identifier of the fourth accounting session corresponding to the fourth QoS flow. The following steps can be included.
  • Step 606 The session management function network element determines that the fourth QoS flow is not mapped to the bearer in the second network, and sends a seventh accounting request message to the AAA server, where the seventh accounting request message includes the second stop indication information and all the identifier of the fourth accounting session corresponding to the fourth QoS flow, and the second stop indication information is used to instruct the AAA server to stop the fourth accounting session.
  • Step 607 The AAA server deletes the information corresponding to the fourth accounting session, and returns a response message.
  • the AAA server determines to delete the resources corresponding to the first QoS flow and the third QoS flow, the following steps may be further included.
  • Step 608 The AAA server sends a disconnection request message to the session management network element, where the disconnection request message includes the identifier of the first accounting session, and the disconnection request message is used to request deletion of the first bearer (That is, the resources corresponding to the original first QoS flow and the third QoS flow).
  • Step 609 the session management network element sends a bearer deletion request to the serving gateway, where the bearer deletion request is used to request deletion of resources corresponding to the first QoS flow and the third QoS flow, and the bearer deletion request may include the identifier of the first bearer .
  • the serving gateway may delete resources such as packet filters corresponding to the first QoS flow and the third QoS flow from the packet filters of the first bearer.
  • Step 610 The network side interacts with the terminal device to complete the process of deactivating the first bearer, and the specific process will not be repeated.
  • the preceding process describes the switching of the terminal device from the 5GS to the EPS, and the embodiments of the present application can also be applied to the process of switching the terminal device from the EPS to the 5GS, which will be described in detail below.
  • an accounting session corresponding to each bearer can be established, and the accounting session can be uniquely identified by an identifier of the accounting session.
  • the flow of FIG. 7 may involve network elements such as a mobility management entity (mobility management entity, MME), a serving gateway, a session management function network element, and an AAA server.
  • MME mobility management entity
  • serving gateway serving gateway
  • session management function network element a session management function network element
  • AAA server an AAA server
  • Step 701 The terminal device performs an attach procedure or a request to establish a PDN connection procedure.
  • Step 702 The serving gateway sends a session creation request message to the session management function network element.
  • the session creation request message may include the identifier of the second bearer in the PDN connection.
  • the network side also needs to perform processes such as authentication and authorization on the terminal device, and the specific process will not be described again. For details, reference may be made to the description in the prior art.
  • the PDN connection includes a second bearer and a third bearer
  • the following describes how to establish an accounting session corresponding to each bearer.
  • an accounting session corresponding to the second bearer may be established through the following steps.
  • Step 703 The session management function network element sends an accounting request message to the AAA server, which is used to request to start accounting for the second bearer in the PDN connection.
  • the content carried in the accounting request message is not limited in the embodiments of the present application, and may include but not limited to the identification of the terminal device (or the user), the address of the terminal device, and the information of the fifth accounting session corresponding to the second bearer.
  • identifier the third charging identifier (the identifier allocated by the session management function network element for the PDN connection), the identifier information of the second bearer (for example, the bearer ID of the second bearer), the wireless access type of the second bearer, and
  • the second bearer corresponds to the QoS document.
  • the identifier of the fifth accounting session may include the following information: the third charging identifier, the address of the network element of the session management function, and the identifier information of the second bearer.
  • the identification information of the second bearer may refer to the bearer identification of the second bearer or other information allocated by the session management function network element for identifying the second bearer.
  • Step 704 The AAA server returns a corresponding response message.
  • the session management function network element may initiate a third bearer establishment process, and the specific process will not be repeated.
  • an accounting session corresponding to the third bearer may be established, which specifically includes the following steps.
  • Step 705 The session management function network element sends an accounting request message to the AAA server, which is used to request to start accounting for the third bearer in the PDN connection.
  • the content carried in the accounting request message is not limited by the embodiments of the present application, and may include but not limited to the identification of the terminal device (or the user), the address of the terminal device, and the information of the sixth accounting session corresponding to the third bearer.
  • the identification of the sixth accounting session may include the following information: the third charging identification or the fourth charging identification, the address of the session management function network element, and the identification information of the third bearer.
  • the identification information of the third bearer may refer to the bearer identification of the third bearer or other information allocated by the session management function network element for identifying the third bearer.
  • the fourth charging identifier is the charging identifier allocated by the session management function network element for the third bearer.
  • Step 706 The AAA server returns a corresponding response message.
  • the session management function network element may respectively send messages of the corresponding functions to the serving gateway, and the messages carry the identifier of the second bearer. For example, when it is decided to modify the second bearer, a modify bearer request (modify bearer request) message is sent; when it is decided to delete the second bearer, a delete bearer request (delete bearer request) is sent, and the specific process will not be repeated.
  • modify bearer request modify bearer request
  • a delete bearer request delete bearer request
  • the session management function network element can update the corresponding accounting session according to each bearer, as shown in FIG. 7 for details.
  • FIG. 7 a schematic flowchart of a communication method provided by an embodiment of the present application is shown.
  • Step 801 The session management function network element determines to map the second bearer to the seventh QoS flow corresponding to the first network, and sends an accounting request message to the AAA server.
  • session management function network element specifically determines to map the second bearer to the seventh QoS flow is not limited in this embodiment of the present application.
  • the accounting request message includes an identifier of the fifth accounting session and information corresponding to the seventh QoS flow, and the accounting request message is used to instruct the AAA server to update the fifth accounting session .
  • Information corresponding to the seventh QoS flow may be used to update the fifth accounting session.
  • the information corresponding to the seventh QoS flow includes one or more of the following:
  • the wireless access type corresponding to the seventh QoS flow; the packet filter corresponding to the seventh QoS flow; and the QoS document corresponding to the seventh QoS flow is the wireless access type corresponding to the seventh QoS flow.
  • the information corresponding to the seventh QoS flow may also be a third charging identifier.
  • Step 802 The AAA server returns a corresponding response message.
  • Step 803 The session management function network element determines to map the third bearer to the eighth QoS flow corresponding to the first network, and sends an accounting request message to the AAA server.
  • the accounting request message includes an identifier of the sixth accounting session and information corresponding to the eighth QoS flow, and the eighth message is used to instruct the AAA server to update the sixth accounting session.
  • the information corresponding to the eighth QoS flow includes one or more of the following:
  • the wireless access type corresponding to the eighth QoS flow; the packet filter corresponding to the eighth QoS flow; and the QoS document corresponding to the eighth QoS flow is the wireless access type corresponding to the eighth QoS flow.
  • Step 804 The AAA server updates the sixth accounting session and returns a corresponding response message.
  • the session management function network element allocates the fourth charging identifier to the third bearer
  • the eighth message further includes the third charging identifier.
  • the AAA server may send a disconnection request message to the session management function network element, and the disconnection request message carries the identifier of the fifth accounting session.
  • the network element of the session management function may delete the resource corresponding to the seventh QoS flow according to the disconnection request message, and the specific process will not be repeated.
  • the session management function network element may include a hardware structure and/or a software module, and implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module . Whether one of the above functions is performed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.
  • each functional module in each embodiment of the present application may be integrated into one processor, or may exist physically alone, or two or more modules may be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules.
  • an embodiment of the present application further provides an apparatus 900 for implementing the function of the session management function network element in the above method.
  • the apparatus may be a software module or a system-on-chip.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the apparatus 900 may include: a processing unit 901 and a communication unit 902 .
  • the communication unit may also be referred to as a transceiver unit, and may include a sending unit and/or a receiving unit, respectively configured to perform the steps of sending and receiving the session management function network element in the above method embodiments.
  • the communication unit 902 may also be referred to as a transceiver, a transceiver, a transceiver, or the like.
  • the processing unit 901 may also be referred to as a processor, a processing board, a processing module, a processing device, or the like.
  • the device for implementing the receiving function in the communication unit 902 may be regarded as a receiving unit, and the device for implementing the transmitting function in the communication unit 902 may be regarded as a transmitting unit, that is, the communication unit 902 includes a receiving unit and a transmitting unit.
  • the communication unit 902 may also sometimes be referred to as a transceiver, a transceiver, or a transceiver circuit or the like.
  • the receiving unit may also sometimes be referred to as a receiver, receiver, or receiving circuit, or the like.
  • the transmitting unit may also sometimes be referred to as a transmitter, a transmitter, or a transmitting circuit, or the like.
  • a processing unit configured to establish a protocol data unit session in the first network for the terminal device, where the protocol data unit session includes a first quality of service flow;
  • a communication unit configured to send a first message to an authentication, authorization and accounting server, where the first message includes an identifier of a first accounting session corresponding to the first quality of service flow;
  • the processing unit configured to map the first quality of service flow to the first bearer corresponding to the second network after the terminal device is switched from the first network to the second network;
  • the communication unit configured to send a second message to the authentication, authorization and accounting server
  • the second message includes the identifier of the first accounting session corresponding to the first quality of service flow and the information of the first bearer, and the second message is used to instruct the authentication and authorization accounting server to update the Describe the first billing session.
  • the communication unit and the processing unit may also perform other operations, for example, the communication unit 902 is configured to perform the sending operation and the receiving operation of the session management function network element in the method embodiment shown in FIG. 4 or FIG. 8 or FIG.
  • the unit 901 is configured to perform other operations of the network element with the session management function in the method embodiment shown in FIG. 4 or FIG. 8 or FIG. 10 except for the sending and receiving operations.
  • the communication unit 902 is configured to perform the sending operation and the receiving operation of the session management function network element in the method embodiment shown in FIG. 4 or FIG. 8 or FIG. 10 except for the sending and receiving operations.
  • FIG. 10 shows another communication apparatus provided by an embodiment of the present application, and the apparatus shown in FIG. 10 may be an implementation of a hardware circuit of the apparatus shown in FIG. 9 .
  • the communication device can be applied to the flow chart shown above to execute the function of the session management function network element in the above method embodiment.
  • FIG. 10 only shows the main components of the communication device.
  • the apparatus 1000 may also include at least one memory 1030 for storing program instructions and/or data.
  • Memory 1030 is coupled to processor 1020 .
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, which may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 1020 may cooperate with the memory 1030 .
  • Processor 1020 may execute program instructions stored in memory 1030 . At least one of the at least one memory may be included in the processor.
  • the apparatus 1000 shown in FIG. 10 includes at least one processor 1020 and a communication interface 1010 , and the processor 1020 is configured to execute the instructions or programs stored in the memory 1030 .
  • the processor 1020 is configured to perform the operations performed by the processing unit 901 in the foregoing embodiments
  • the communication interface 1010 is configured to perform the operations performed by the communication unit 902 in the foregoing embodiments.
  • the communication interface may be a transceiver, a circuit, a bus, a module, or other types of communication interfaces.
  • the transceiver when the communication interface is a transceiver, the transceiver may include an independent receiver and an independent transmitter; it may also be a transceiver integrating a transceiver function, or a communication interface.
  • the apparatus 1000 may also include a communication line 1040 .
  • the communication interface 1010, the processor 1020 and the memory 1030 may be connected to each other through a communication line 1040; the communication line 1040 may be a peripheral component interconnect (PCI for short) bus or an extended industry standard architecture (extended industry standard architecture). , referred to as EISA) bus and so on.
  • the communication line 1040 can be divided into an address bus, a data bus, a control bus, and the like. For ease of presentation, only one thick line is used in FIG. 10, but it does not mean that there is only one bus or one type of bus.
  • the present application also provides a computer-readable storage medium for storing a computer program, where the computer program includes instructions for executing the method provided in any of the above processes.
  • the present application also provides a computer program product, the computer program product includes: computer program code, when the computer program code is run on a computer, the computer is made to execute the method provided in any of the above procedures.
  • the present application also provides a chip, including a processor, which is coupled to a memory and configured to execute a computer program or instruction stored in the memory.
  • a processor which is coupled to a memory and configured to execute a computer program or instruction stored in the memory.
  • the processor executes the computer program or instruction, the processor causes the The methods provided in any of the above flows are implemented.
  • the embodiments of the present application may be provided as a method, a system, or a computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) having computer-usable program code embodied therein.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory result in an article of manufacture comprising instruction means, the instructions
  • the apparatus implements the functions specified in the flow or flow of the flowcharts and/or the block or blocks of the block diagrams.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

一种通信方法及装置，其中方法包括：会话管理功能网元为终端设备在第一网络中建立包括第一服务质量流的协议数据单元会话之后，终端设备从第一网络切换到第二网络时，如果确定将第一服务质量流映射到在第二网络中的第一承载，则可以向认证授权记账服务器发送包括第一服务质量流对应的第一记账会话的标识和第一承载的信息的第二消息，从而通过第二消息用于指示认证授权记账服务器更新第一记账会话。通过上面的过程，当终端设备从第一网络切换到第二网络时，会话管理功能网元指示认证授权记账服务器根据第一承载的信息更新第一记账会话，从而实现在切换到第二网络之后，根据第一记账会话的信息对终端设备通过第一承载传输的业务进行计费等控制。

Description

一种通信方法及装置 技术领域
本申请涉及无线通信技术领域，特别涉及一种通信方法及装置。
背景技术
在移动蜂窝网络中，可以通过为终端设备分配记账会话(accounting session)实现计费等功能。在第五代系统(the 5rd generation system，5GS)中，会话管理功能(session management function，SMF)网元是按照协议数据单元(protocol data unit，PDU)会话粒度分配记账会话，即为不同PDU会话分配不同的记账会话。而在演进的分组系统(evolved packet system，EPS)中，SMF可以为不同的EPS承载(bearer)分配不同的记账会话。
综上可知，由于在不同移动蜂窝网络中，SMF网元按照不同粒度分配记账会话，因此当终端设备从5GS切换到EPS，或者从EPS切换到5GS时，如何更新记账会话是一个亟待解决的问题。
发明内容
本申请实施方式的目的在于提供一种通信方法及装置，用以解决终端设备在不同移动蜂窝网络间进行切换时，如何实现记账会话的更新的问题。
第一方面，本申请实施例提供一种通信方法，包括：会话管理功能网元为终端设备在第一网络中建立包括第一服务质量流的协议数据单元会话之后，可以通过第一消息向认证授权记账服务器指示第一服务质量流对应的第一记账会话的标识；当终端设备从第一网络切换到第二网络时，如果会话管理功能网元确定将第一服务质量流映射到在第二网络中的第一承载，则可以向认证授权记账服务器发送包括第一服务质量流对应的第一记账会话的标识和第一承载的信息的第二消息，从而通过第二消息用于指示认证授权记账服务器更新第一记账会话。
通过上面的过程，当终端设备从第一网络切换到第二网络时，会话管理功能网元指示认证授权记账服务器根据第一承载的信息更新第一记账会话，从而实现在切换到第二网络之后，根据第一记账会话的信息对终端设备通过第一承载传输的业务访问进行控制，譬如接入控制，计费和业务提供等。
一种可能的实现方式中，所述协议数据单元会话还包括第二服务质量流，所述会话管理功能网元可以通过第三消息向认证授权记账服务器指示第二服务质量流对应的第二记账会话的标识；当终端设备从第一网络切换到第二网络时，如果会话管理功能网元确定将所述第二服务质量流映射到所述第一承载，则可以向所述认证授权记账服务器发送第四消息，其中，所述第四消息包括所述第二服务质量流对应的第二记账会话的标识和所述第一承载的信息，所述第四消息用于指示所述认证授权记账服务器更新所述第二记账会话。
通过上面的过程，当终端设备从第一网络切换到第二网络时，会话管理功能网元指示AAA服务器根据第一承载的信息更新第二记账会话，从而实现在切换到第二网络之后，根据第二记账会话的信息对终端设备通过第一承载传输的业务访问进行控制，譬如接入控制，计费和业务提供等。
一种可能的实现方式中，所述会话管理功能网元向认证授权记账服务器发送第二消息之后，所述方法还包括：会话管理功能网元接收来自所述认证授权记账服务器的断开连接请求消息，所述断开连接请求消息包括所述第一记账会话的标识，所述断开连接请求消息用于请求删除所述第一服务质量流对应的资源；所述会话管理功能网元向服务网关发送更新承载请求，所述更新承载请求用于请求删除所述第一服务质量流对应的资源。
通过上面的方法，可以通过携带记账会话的标识，灵活的对记账会话进行修改和删除等操作。
一种可能的实现方式中，所述协议数据单元会话还包括第三服务质量流；所述方法还包括：所述会话管理功能网元将所述终端设备的所述第三服务质量流映射到所述第一承载；所述会话管理功能网元向所述认证授权记账服务器发送第一停止指示信息和所述第三服务质量流对应的第三记账会话的标识，所述第一停止指示信息用于指示所述认证授权记账服务器停止所述第三记账会话。
通过上面的方法，由于多个服务质量流映射到第一承载，可以只更新其中一个服务质量流对应的记账会话，例如只更新第一服务质量流对应的第一记账会话，避免管理太多冗余的记账会话，从而提高记账会话的管理效率。
一种可能的实现方式中，所述协议数据单元会话还包括第四服务质量流，所述方法还包括：所述会话管理功能网元向所述认证授权记账服务器发送第五消息，所述第五消息包括所述第四服务质量流对应的第四记账会话的标识；所述会话管理功能网元确定所述终端设备从所述第一网络切换到所述第二网络后，确定所述第四服务质量流不映射到所述第二网络中的承载；所述会话管理功能网元向所述认证授权记账服务器发送第二停止指示信息和所述第四服务质量流对应的第四记账会话的标识，所述第二停止指示信息用于指示所述认证授权记账服务器停止所述第四记账会话。
通过上面的方法，由于第四服务质量流不映射到任一承载，可以停止所述第四服务质量流对应的第四记账会话，避免管理太多冗余的记账会话，从而提高记账会话的管理效率。
一种可能的实现方式中，所述第一记账会话的标识包括第一计费标识、所述会话管理功能网元的地址以及所述第一服务质量流的标识信息，所述第一计费标识是所述会话管理功能网元为所述协议数据单元会话分配的计费标识。
一种可能的实现方式中，所述第二记账会话的标识包括第一计费标识、所述会话管理功能网元的地址以及所述第二服务质量流的标识信息。
一种可能的实现方式中，所述第一承载的信息包括以下至少一项：所述第一承载对应的无线接入类型；所述第一承载对应的服务质量文档。
一种可能的实现方式中，所述第一承载的信息中还包括所述会话管理功能网元为所述第一承载分配的第二计费标识。
一种可能的实现方式中，所述方法还包括：所述会话管理功能网元确定所述终端设备从所述第二网络切换到所述第一网络后，将所述第一承载映射到在所述第一网络中所对应的第五服务质量流；所述会话管理功能网元向所述认证授权记账服务器发送第六消息；其中，所述第六消息包括所述第一记账会话的标识和所述第五服务质量流对应的信息，所述第六消息用于指示所述认证授权记账服务器更新所述第一记账会话。
通过上面的过程，当终端设备从第二网络切换到第一网络后，会话管理功能网元指示认证授权记账服务器根据第五服务质量流对应的信息更新第一记账会话，从而实现在切换 到第一网络之后，根据第一记账会话的信息对用户通过第五服务质量流传输的业务访问进行控制，譬如接入控制，计费和业务提供等。
一种可能的实现方式中，所述第五服务质量流对应的信息包括以下一项或多项：
所述第五服务质量流对应的无线接入类型；所述第五服务质量流对应的服务质量文档。
一种可能的实现方式中，所述第五服务质量流对应的信息还包括所述第一计费标识。
一种可能的实现方式中，所述方法还包括：所述会话管理功能网元确定所述终端设备从所述第二网络切换到所述第一网络后，将所述第一承载映射到在所述第一网络中所对应的第六服务质量流；所述会话管理功能网元向所述认证授权记账服务器发送第七消息；其中，所述第七消息包括所述第二记账会话的标识和所述第六服务质量流对应的信息，所述第六消息用于指示所述认证授权记账服务器更新所述第二记账会话。
第二方面，本申请还提供一种通信装置，该通信装置具有实现上述第一方面提供的任一方法。该通信装置可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种可能的实现方式中，该通信装置包括：处理器，该处理器被配置为支持该通信装置执行以上所示方法中会话管理功能网元的相应功能。该通信装置还可以包括存储器，该存储可以与处理器耦合，其保存该通信装置必要的程序指令和数据。可选地，该通信装置还包括通信接口，该通信接口用于支持该通信装置与认证授权记账服务器等设备之间的通信。
在一种可能的实现方式中，该通信装置包括相应的功能单元，分别用于实现以上方法中的步骤。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的单元。
在一种可能的实施方式中，通信装置的结构中包括处理单元和通信单元，这些单元可以执行上述方法示例中相应功能，具体参见第一方面提供的方法中的描述，此处不做赘述。
第三方面，本申请实施例提供一种通信方法，包括：会话管理功能网元为终端设备在第二网络中建立第一承载；所述会话管理功能网元确定所述终端设备从所述第二网络切换到所述第一网络后，将所述第一承载映射到在所述第一网络中所对应的第五服务质量流；所述会话管理功能网元向所述认证授权记账服务器发送第六消息；其中，所述第六消息包括所述第一记账会话的标识和所述第五服务质量流对应的信息，所述第六消息用于指示所述认证授权记账服务器更新所述第一记账会话。
通过上面的过程，当终端设备从第二网络切换到第一网络后，会话管理功能网元指示认证授权记账服务器根据第五服务质量流对应的信息更新第一记账会话，从而实现在切换到第一网络之后，根据第一记账会话的信息对终端设备通过第五服务质量流传输的业务访问进行控制，譬如接入控制，计费和业务提供等。
一种可能的实现方式中，所述第五服务质量流对应的信息包括以下一项或多项：
所述第五服务质量流对应的无线接入类型；所述第五服务质量流对应的服务质量文档。
一种可能的实现方式中，所述第五服务质量流对应的信息还包括所述第一计费标识。
一种可能的实现方式中，所述方法还包括：所述会话管理功能网元确定所述终端设备从所述第二网络切换到所述第一网络后，将所述第一承载映射到在所述第一网络中所对应的第六服务质量流；所述会话管理功能网元向所述认证授权记账服务器发送第七消息；其中，所述第七消息包括所述第二记账会话的标识和所述第六服务质量流对应的信息，所述 第六消息用于指示所述认证授权记账服务器更新所述第二记账会话。
第四方面，本申请还提供一种通信装置，该通信装置具有实现上述第三方面提供的任一方法。该通信装置可以通过硬件实现，也可以通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述功能相对应的单元或模块。
在一种可能的实现方式中，该通信装置包括：处理器，该处理器被配置为支持该通信装置执行以上所示方法中会话管理功能网元的相应功能。该通信装置还可以包括存储器，该存储可以与处理器耦合，其保存该通信装置必要的程序指令和数据。可选地，该通信装置还包括通信接口，该通信接口用于支持该通信装置与认证授权记账服务器等设备之间的通信。
在一种可能的实现方式中，该通信装置包括相应的功能单元，分别用于实现以上方法中的步骤。功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。硬件或软件包括一个或多个与上述功能相对应的单元。
在一种可能的实施方式中，通信装置的结构中包括处理单元和通信单元，这些单元可以执行上述方法示例中相应功能，具体参见第三方面提供的方法中的描述，此处不做赘述。
第五方面，本申请提供一种芯片，包括处理器，所述处理器与存储器耦合，用于执行所述存储器中存储的计算机程序或指令，当所述处理器执行所述计算机程序或指令时，使得第一方面至或第一方面中任一种可能实现方式中的方法被实现，或者使得第三方面至或第三方面中任一种可能实现方式中的方法被实现。
第六方面，本申请提供一种通信装置，所述通信装置包括处理器，当所述处理器执行存储器中的计算机程序或指令时，如第一方面或第一方面中任一种可能实现方式中的方法被执行，或者如第三方面或第三方面中任一种可能实现方式中的方法被执行。
第七方面，本申请提供一种通信装置，所述通信装置包括处理器和存储器，所述存储器用于存储计算机程序或指令；所述处理器用于执行所述存储器所存储的计算机程序或指令，以使所述通信装置执行如第一方面或第一方面中任一种可能实现方式中的方法，或者以使所述通信装置执行如第三方面或第三方面中任一种可能实现方式中的方法。
第八方面，本申请提供一种通信装置，所述通信装置包括处理器、存储器和收发器，所述收发器，用于接收信号或者发送信号；所述存储器，用于存储计算机程序或指令；所述处理器，用于从所述存储器调用所述计算机程序或指令执行如第一方面或第一方面中任一种可能实现方式中的方法；或者，所述处理器，用于从所述存储器调用所述计算机程序或指令执行如第三方面或第三方面中任一种可能实现方式中的方法。
第九方面，提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序包括用于执行第一方面或第一方面中任一种可能实现方式中的方法的指令，或者该计算机程序包括用于执行第三方面或第三方面中任一种可能实现方式中的方法的指令。
第十方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述第一方面或第一方面中任一种可能实现方式中的方法，或者使得计算机执行上述第三方面或第三方面中任一种可能实现方式中的方法。
附图说明
图1为适用于本申请实施例的一种网络架构示意图；
图2为本申请实施例提供的一种通信方法流程示意图；
图3为本申请实施例提供的在5GS中建立PDU会话的流程示意图；
图4为本申请实施例提供的一种从5GS切换到EPS时记账会话更新示意图；
图5为本申请实施例提供的一种从EPS切换到5GS时记账会话更新示意图；
图6为本申请实施例提供的一种从5GS切换到EPS时记账会话更新示意图；
图7为本申请实施例提供的一种为EPS中的承载建立记账会话的示意图；
图8为本申请实施例提供的一种从EPS切换到5GS时记账会话更新示意图；
图9为本申请实施例提供的一种通信装置结构示意图；
图10为本申请实施例提供的一种通信装置结构示意图。
具体实施方式
下面将结合附图对本申请实施例作进一步地详细描述。
本申请实施例的技术方案可以应用于各种移动蜂窝系统，例如：5GS以及EPS等。其中，5GS包括但不限于新无线(new radio，NR)系统；EPS包括但不限于长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)等，在此不做限制。
如图1所示，为适用于本申请实施例的一种网络架构示意图。图1中，终端设备通过无线接入网(radio access network，RAN)设备接入5GS之后，位于数据网络(data network)中的认证授权记账(authentication authorization and accounting，AAA)服务器可以对终端设备进行认证、授权和记账。其中，AAA服务器可以支持远程用户拨号认证(remote authentication dial in user service，RADIUS)和Diameter协议。图1所示的网络中还包括接入和移动性管理功能(access and mobility management function，AMF)网元、SMF网元以及用户面功能(user plane function，UPF)等，上述各个网元的功能可以参考现有技术中的描述，在此不再赘述。
如前所述，在5GS中，SMF网元为不同PDU会话分配不同的记账会话。每个记账会话对应一个记账会话标识(accounting session identity，acct-session-ID)或会话标识(session-ID)，其中，5GS与AAA服务器采用RADIUS协议通信时，记账会话对应的标识为acct-session-ID；5GS与AAA服务器采用diameter协议通信时，记账会话对应的标识为(session-ID)，记账会话标识或会话标识用于全局唯一标识一个记账会话。其中记账会话标识中包括计费标识(charging ID)和SMF网元的地址等信息。举例来说，SMF网元的地址可以为SMF网元的计费地址，具体可以是指SMF网元的互联网协议(internet protocol，IP)地址等信息。
本申请实施例的流程中，以记账会话对应的标识为acct-session-ID为例进行描述，在实际应用中，记账会话对应的标识也可以为session-ID，区别在于session-ID的取值由会话管理功能网元动态分配，并且保持全局唯一。
在5GS中，由于SMF网元为PDU会话分配一个计费标识，所以PDU会话中的多个服务质量(quality of service，QoS)流(flow)对应的记账会话标识中的计费标识是相同的，即PDU会话中的多个QoS流对应的记账会话标识是相同的，该PDU会话的记账会话标识无法标识该PDU会话中不同的QoS流。
5GS中的PDU会话，在EPS中称为分组数据网络(packet data network，PDN)连接， 一个PDN连接中有多个承载(bearer)，而在EPS中，SMF网元可以为不同的承载分配不同的计费标识，也就是说，PDN连接中的每个承载对应的记账会话标识不同。
如果终端设备在不同网络中进行切换，例如从5GS切换到EPS，由于5GS中PDU会话包括的多个QoS流对应相同的记账会话，EPS中与QoS流对等的承载对应不同的记账会话，由于不同网络中，记账会话的分配粒度是不同的，终端设备切换到EPS之后，如何更新属于一个PDU会话的多个QoS流对应的记账会话，目前还没有一个明确的解决方案。
本申请实施例中，终端设备，可以为具有无线收发功能的设备或可设置于任一设备中的芯片，也可以称为用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、无线通信设备、用户代理或用户装置。本申请实施例中的终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、虚拟现实(virtual reality，VR)终端、增强现实(augmented reality，AR)终端、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。
接入网设备，可以是5GS中的下一代基站(generation node B，gNB)，可以是EPS中的演进型基站(evolutional node B，eNB)等。
需要说明的是，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。结合前面的描述，如图2所示，为本申请实施例提供的一种通信方法流程示意图。参见图2，该方法包括：
步骤201：会话管理功能网元为终端设备在第一网络中建立PDU会话，所述PDU会话包括第一QoS流。
其中，所述第一网络可以是指5GS，相应的，会话管理功能网元可以是指SMF网元，也可以是指同时具有SMF网元和控制面PDN网关(packet data network gateway for control plane，PGW-C)功能的网元。
会话管理功能网元具体如何建立PDU会话，本申请实施例并不限定，具体过程不再赘述。其中PDU会话中除了包括第一QoS流之外，还可以包括第二QoS流、第三QoS流以及第四QoS流等，具体包括的QoS流的数量，本申请实施例对此并不限定。
需要说明的是，PDU会话中包括的QoS流可以分为默认QoS流和专有QoS流，第一QoS流可以为默认QoS流，也可以为专有QoS流，本申请实施例对此并不限定。
步骤202：会话管理功能网元向AAA服务器发送第一消息，所述第一消息包括所述第一QoS流对应的第一记账会话的标识。
其中，第一记账会话的标识是会话管理功能网元分配的。本申请实施例中，第一记账会话的标识可以包括但不限于以下信息：第一计费标识、会话管理功能网元的地址以及第一QoS流的标识信息。所述第一计费标识是所述会话管理功能网元为所述PDU会话分配的计费标识，例如可以是为所述PDU会话中的默认QoS流分配的标识。会话管理功能网元的地址可以是指会话管理功能网元的IP地址。第一QoS流的标识信息可以是指第一QoS流的QoS流标识(QoS flow identifier，QFI)或会话管理功能网元分配的其他用于标识第 一QoS流的信息。
需要说明的是，现有技术中，PDU会话可以包括多个不同的QoS流，但是记账会话是针对PDU会话进行分配的，也即是说现有技术中是针对PDU会话进行记账的，没有针对这些QoS流分别进行记账的具体实现。本申请实施例中，针对PDU会话中的每个QoS流，将PDU会话的记账会话标识中加入QoS流的标识信息，从而实现为不同QoS流分配不同的记账会话标识，从而可以实现针对PDU会话中的每个QoS流分别进行记账。
步骤203：会话管理功能网元确定终端设备从第一网络切换到第二网络后，将第一QoS流映射到在第二网络中所对应的第一承载。
具体的，所述会话管理功能网元可以确定所述第一QoS流在第二网络中所对应的第一承载的标识，所述会话管理功能网元可以向所述第二网络发送第一承载的标识，用于请求第二网络建立所述第一承载。
其中，所述第二网络可以是指EPS。会话管理功能网元具体如何确定终端设备切换到第二网络，本申请实施例对此并不限定，具体可以参考现有技术中的描述，在此不再赘述。
步骤204：会话管理功能网元向AAA服务器发送第二消息。
其中，所述第二消息包括所述第一QoS流对应的第一记账会话的标识和所述第一承载的信息，第一承载的信息可以用于更新第一记账会话的标识，所述第二消息用于指示所述AAA服务器更新所述第一记账会话。
其中，所述第一承载的信息包括以下至少一项：
所述第一承载对应的无线接入类型；所述第一承载对应的QoS文档；所述第一承载对应的分组过滤器；会话管理网元为所述第一承载分配的第二计费标识。
通过上面的过程，当终端设备从第一网络切换到第二网络时，会话管理功能网元指示AAA服务器根据第一承载的信息更新第一记账会话，从而实现在切换到第二网络之后，根据第一记账会话的信息对终端设备通过第一承载传输的业务访问进行控制，譬如接入控制，计费和业务提供等。
如前所述，本申请实施例中，会话管理功能网元可以为终端设备在第一网络中建立PDU会话，并为所述PDU会话中的不同QoS流分配不同的记账会话的标识，下面详细描述。
如图3所示，当终端设备通过5GS接入时，可以建立QoS流对应的记账会话，并用记账会话的标识来唯一标识每个QoS流的记账会话，其中记账会话的标识包括该QoS流的标识信息。需要说明的是，图3所示的流程是基于现有文献TS 23.502中关于PDU会话建立的相关内容，具体可以参考上述文献。
步骤301：终端设备通过发送PDU会话建立请求消息发起PDU会话建立流程，PDU会话建立请求消息中包括认证、授权等信息。
步骤302：AMF网元向会话管理功能网元发送PDU会话建立上下文请求消息。
该消息的具体名称并不限定，例如可以为Nsmf_PDUSession_CreateSMContext Request等，该消息中可以包括认证、授权等信息。
步骤303：会话管理功能网元向AMF网元发送响应消息。
可选的，如果PDU会话对应的N4会话还没有建立，则会话管理功能网元需要发起N4会话建立流程，具体过程不再赘述。
进一步的，网络侧还需要对终端设备进行认证、授权等过程，具体过程不再描述，具体可以参考TS 23.502中等文献中的描述。
假设图3所述的流程中，PDU会话包括第一QoS流、第二QoS流、第三QoS流以及第四QoS流，下面分别描述如何建立每个QoS流对应的记账会话。
对于PDU会话中的第一QoS流，可以通过以下步骤建立第一QoS流对应的记账会话。
步骤304：会话管理功能网元向AAA服务器发送记账请求(accounting-request)消息，用于请求开始对PDU会话中的第一QoS流进行记账。
该记账请求消息可以是指图2流程中的第一消息，记账请求消息中携带的内容，本申请实施例并不限定，可以包括但不限于终端设备(或者称为用户)的标识、终端设备的地址、第一QoS流对应的第一记账会话的标识(以下记作记账会话标识1)、第一计费标识(会话管理功能网元为PDU会话分配的标识)、第一QoS流的QFI(以下记作第一QFI)、无线接入类型(5GS中的无线接入类型为下一代(next generation RAN，NG-RAN))、第一QoS流的分组过滤器(packet filter)以及第一QoS流对应的QoS文档。
记账会话标识1可以包括以下信息：第一计费标识、会话管理功能网元的地址以及第一QoS流的标识信息。第一QoS流的标识信息可以是指第一QoS流的第一QFI或会话管理功能网元分配的其他用于标识第一QoS流的信息。
步骤305：AAA服务器返回相应的响应消息。
可选的，会话管理功能网元决定在PDU会话中创建新的第二QoS流时，会话管理功能网元可以发起第二QoS流建立流程，具体过程不再赘述。在PDU会话中建立第二QoS流之后，可以建立第二QoS流对应的记账会话，具体包括以下步骤。
步骤306：会话管理功能网元向AAA服务器发送记账请求消息，用于请求开始对PDU会话中的第二QoS流进行记账。
该记账请求消息可以存在其他名称，例如可以是第三消息。该记账请求消息中携带的内容，本申请实施例并不限定，可以包括但不限于终端设备的标识、终端设备的地址、第二QoS流对应的第二记账会话的标识(以下记作记账会话标识2)、第一计费标识、第二QoS流的QFI(记作第二QFI)、无线接入类型(5GS中的无线接入类型为NG-RAN)、第二QoS流上的过滤器以及第二QoS流对应的QoS文档。
记账会话标识2可以包括以下信息：第一计费标识、会话管理功能网元的地址以及第二QoS流的标识信息。第二QoS流的标识信息可以是指第二QoS流的第二QFI或会话管理功能网元分配的其他用于标识第二QoS流的信息。
步骤307：AAA服务器返回相应的响应消息。
同样的，当会话管理功能网元决定在PDU会话中创建第三QoS流以及第四QoS流时，可以采用上面同样的方法建立第三QoS流对应的第三记账会话的标识，以及第四QoS流对应的第四记账会话的标识，具体过程不再赘述。
其中，第三记账会话的标识可以包括以下信息：第一计费标识、会话管理功能网元的地址以及第三QoS流的标识信息。第三QoS流的标识信息可以是指第三QoS流的第三QFI或会话管理功能网元分配的其他用于标识第三QoS流的信息。第四记账会话的标识可以包括以下信息：第一计费标识、会话管理功能网元的地址以及第四QoS流的标识信息。第四QoS流的标识信息可以是指第四QoS流的第四QFI或会话管理功能网元分配的其他用于标识第四QoS流的信息。
结合前面的流程，当终端设备从第一网络切换到第二网络时，会话管理功能网元可以根据每个QoS流对应的承载更新每个QoS流对应的记账会话。若存在多个QoS流映射到同一个承载，则会话管理功能网元为每个记账会话更新承载对应的信息，下面结合图4详细描述。
步骤401：终端设备从5GS切换到EPS。
终端设备切换到EPS的具体过程，本申请实施例不再赘述，具体可以参考现有技术中的描述。
终端设备从5GS切换到EPS之后，会话管理功能网元确定将PDU会话中的第一QoS流和第二QoS流映射到第一承载时，可以执行以下步骤。
需要说明的是，会话管理功能网元具体如何确定将第一QoS流和第二QoS流映射到第一承载，本申请实施例对此并不限定。
步骤402：会话管理功能网元向AAA服务器发送第一记账请求消息。
所述第一记账请求消息可以是指图2流程中的第二消息。第一记账请求消息包括第一QoS流对应的第一记账会话的标识和第一承载的信息，第一承载的信息用于更新第一记账会话，所述第一记账请求消息用于指示所述AAA服务器更新第一QoS流对应的第一记账会话。
其中，所述第一承载的信息包括以下至少一项：
所述第一承载对应的无线接入类型，例如在EPS中，第一承载的无线接入类型可以是指演进型通用陆地无线接入网(evolved universal terrestrial radio access network，E-UTRAN)；所述第一承载对应的分组过滤器；所述第一承载对应的QoS文档。
可选的，当会话管理网元为所述第一承载分配第二计费标识时，第一承载的信息中还包括第二计费标识。
步骤403：AAA服务器对第一记账会话进行更新，并返回响应消息。
举例来说，AAA服务器可以将第一记账会话中的第一计费标识更新为第二计费标识等，实现更新第一记账会话。
步骤404：会话管理功能网元向AAA服务器发送第二记账请求消息。
所述第二记账请求消息可以存在其他名称，例如可以是第四消息。第二记账请求消息包括第二QoS流对应的第二记账会话的标识和第一承载的信息，第一承载的信息用于更新第二记账会话，所述第二记账请求消息用于指示所述AAA服务器更新第二QoS流对应的第二记账会话。
其中，所述第一承载的信息可以参考前面的描述，在此不再赘述。
可选的，当会话管理网元为所述第一承载分配第二计费标识时，第一承载的信息中还包括第二计费标识。
步骤405：AAA服务器对第二记账会话进行更新，并返回响应消息。
举例来说，AAA服务器可以将第二记账会话中的第一计费标识更新为第二计费标识等，实现更新第一记账会话。
需要说明的是，经过步骤403和步骤405两步，AAA服务器对第二记账会话进行更新之后，会根据第一承载来进行记账，即针对两个QoS流都只基于第一承载进行记账，不再基于QoS流进行记账。虽然第一QoS流和第二QoS流映射到第一承载，但是会话管理功能网元仍然保持每个QoS流对应的分组过滤器。
可选的，当AAA服务器确定删除第一QoS流对应的资源时，还可以包括以下步骤。
步骤406：AAA服务器向会话管理网元发送断开连接请求消息，所述断开连接请求消息包括所述第一记账会话的标识，所述断开连接请求消息用于请求删除所述第一QoS流对应的资源。
步骤407：会话管理网元向服务网关发送更新承载请求，所述更新承载请求用于请求删除所述第一QoS流对应的资源，所述更新承载请求中可以包括第一承载的标识。
服务网关接收到更新承载请求之后，可以从第一承载的分组过滤器中删除第一QoS流对应的分组过滤器等资源。
步骤408：网络侧与终端设备进行交互，完成第一承载的更新流程，具体过程不再赘述。
可选的，当AAA服务器确定删除第二QoS流对应的资源时，还可以包括以下步骤。
步骤409：AAA服务器向会话管理网元发送断开连接请求消息，所述断开连接请求消息包括所述第二记账会话的标识，所述断开连接请求消息用于请求删除所述第二QoS流对应的资源。
会话管理网元确定第一承载对应的第二QoS流删除之后，第一承载不存在对应的QoS流，则可以执行以下步骤。
步骤410：会话管理网元向服务网关发送删除承载请求，所述删除承载请求用于请求删除所述第二QoS流对应的资源，所述删除承载请求中可以包括第一承载的标识。
服务网关接收到删除承载请求之后，可以从第一承载的分组过滤器中删除第二QoS流对应的分组过滤器等资源。
步骤411：网络侧与终端设备进行交互，完成删除第一承载的流程，也就是完成去激活(deactive)第一承载的流程，具体过程不再赘述。
基于图4的流程步骤401-步骤405的流程，若后续终端设备从EPS切换到5GS之后，会话管理功能网元确定将第一承载映射到第五QoS流程和第六QoS流程，具体步骤如图5所示：
步骤501：会话管理功能网元确定将第一承载映射到在第一网络中所对应的第五QoS流，向AAA服务器发送第三记账请求消息。
需要说明的是，会话管理功能网元具体如何确定将第一承载映射到第五QoS流，本申请实施例对此并不限定。
其中，所述第三记账请求消息包括所述第一记账会话的标识和所述第五QoS流对应的信息，所述第三记账请求消息用于指示所述AAA服务器更新所述第一记账会话。第一QoS流对应的信息可以用于更新第一记账会话。
所述第五QoS流对应的信息包括以下一项或多项：
所述第五QoS流对应的无线接入类型；所述第五QoS流对应的分组过滤器；所述第五QoS流对应的QoS文档。
若在步骤402中，会话管理网元为所述第一承载分配第二计费标识时，则所述第五QoS流对应的信息中还包括第一计费标识。
步骤502：AAA服务器对第一记账会话进行更新，并返回相应的响应消息。
步骤503：会话管理功能网元确定将所述第一承载映射到在所述第一网络中所对应的第六QoS流，向AAA服务器发送第四记账请求消息。
其中，所述第四记账请求消息包括第二记账会话的标识和所述第六QoS流对应的信息，所述第四记账请求消息用于指示所述AAA服务器更新所述第二记账会话。
所述第六QoS流对应的信息包括以下一项或多项：
所述第六QoS流对应的无线接入类型；所述第六QoS流对应的分组过滤器；所述第六QoS流对应的QoS文档。
若在步骤404中，会话管理网元为所述第一承载分配第二计费标识时，则所述第六QoS流对应的信息中还包括第一计费标识。
步骤504：AAA服务器对第二记账会话进行更新，并返回相应的响应消息。
本申请实施例中，当终端设备从第一网络切换到第二网络时，会话管理功能网元可以根据每个QoS流对应的承载更新每个QoS流对应的记账会话。若存在多个QoS流映射到同一个承载，会话管理功能网元还可以更新一个记账会话，并停止其他记账会话，下面结合图6详细描述。
步骤601：终端设备从5GS切换到EPS。
终端设备切换到EPS的具体过程，本申请实施例不再赘述，具体可以参考现有技术中的描述。
终端设备从5GS切换到EPS之后，会话管理功能网元确定将PDU会话中的第一QoS流和第三QoS流映射到第一承载时，可以执行以下步骤。
需要说明的是，会话管理功能网元具体如何确定将第一QoS流和第三QoS流映射到第一承载，本申请实施例对此并不限定。
步骤602：会话管理功能网元向AAA服务器发送第五记账请求消息。
所述第五记账请求消息可以是指图2流程中的第二消息。第五记账请求消息包括第一QoS流对应的第一记账会话的标识和第一承载的信息，第一承载的信息用于更新第一记账会话，所述第五记账请求消息用于指示所述AAA服务器更新第一QoS流对应的第一记账会话。第一承载的信息的具体内容可以参考前面的描述。
可选的，所述第五记账请求消息中还可以包括第一QoS流的分组过滤器和第三QoS流的分组过滤器汇聚后的分组过滤器。
步骤603：AAA服务器对第一记账会话进行更新，并返回响应消息。
将PDU会话中的第一QoS流和第三QoS流映射到第一承载之后，可以将第三QoS流对应的第三记账会话停止。
步骤604：会话管理功能网元向AAA服务器发送第六记账请求消息。
所述第六记账请求消息包括第一停止指示信息和第三QoS流对应的第三记账会话的标识，所述第一停止指示信息用于指示所述AAA服务器停止所述第三记账会话。
步骤605：AAA服务器删除第三记账会话对应的信息，并返回响应消息。
需要说明的是，经过步骤503和步骤505两步，AAA服务器停止第三记账会话后，根据第一记账会话的信息对用户通过第一承载传输的业务访问进行控制，譬如接入控制，计费和业务提供等。
可选的，如果PDU会话还包括第四QoS流，在建立第四QoS流时，会话管理功能网元可以通过第五消息向AAA服务器发送第四QoS流对应的第四记账会话的标识。当终端设备切换到EPS之后，会话管理功能网元确定第四QoS流不映射到EPS网络中的任一承载，则可以指示AAA服务器删除第四QoS流对应的第四记账会话的标识，具体可以包括 以下步骤。
步骤606：会话管理功能网元确定第四QoS流不映射到所述第二网络中的承载，向AAA服务器发送第七记账请求消息，第七记账请求消息包括第二停止指示信息和所述第四QoS流对应的第四记账会话的标识，所述第二停止指示信息用于指示所述AAA服务器停止所述第四记账会话。
步骤607：AAA服务器删除第四记账会话对应的信息，并返回响应消息。
可选的，当AAA服务器确定删除第一QoS流和第三QoS流对应的资源时，还可以包括以下步骤。
步骤608：AAA服务器向会话管理网元发送断开连接请求消息，所述断开连接请求消息包括所述第一记账会话的标识，所述断开连接请求消息用于请求删除第一承载(即原来第一QoS流和第三QoS流)对应的资源。
步骤609：会话管理网元向服务网关发送删除承载请求，所述删除承载请求用于请求删除第一QoS流和第三QoS流对应的资源，所述删除承载请求中可以包括第一承载的标识。
服务网关接收到删除承载请求之后，可以从第一承载的分组过滤器中删除第一QoS流和第三QoS流对应的分组过滤器等资源。
步骤610：网络侧与终端设备进行交互，完成去激活第一承载的流程，具体过程不再赘述。
前面的流程描述了终端设备从5GS切换到EPS，本申请实施例还可以适用于终端设备从EPS切换到5GS的过程，下面详细描述。
如图7所示，当终端设备通过EPS接入时，可以建立每个承载对应的记账会话，并用记账会话的标识来唯一标识这个记账会话。图7的流程可能涉及到移动性管理实体(mobility management entity，MME)、服务网关、会话管理功能网元以及AAA服务器等网元。
步骤701：终端设备执行附着流程或请求建立PDN连接流程。
步骤702：服务网关向会话管理功能网元发送创建会话请求消息。
创建会话请求消息中可以包括PDN连接中第二承载的标识。
进一步的，网络侧还需要对终端设备进行认证、授权等过程，具体过程不再描述，具体可以参考现有技术中的描述。
假设图7所述的流程中，PDN连接包括第二承载以及第三承载，下面分别描述如何建立每个承载对应的记账会话。
对于第二承载，可以通过以下步骤建立第二承载对应的记账会话。
步骤703：会话管理功能网元向AAA服务器发送记账请求消息，用于请求开始对PDN连接中的第二承载进行记账。
该记账请求消息中携带的内容，本申请实施例并不限定，可以包括但不限于终端设备(或者称为用户)的标识、终端设备的地址、第二承载对应的第五记账会话的标识、第三计费标识(会话管理功能网元为PDN连接分配的标识)、第二承载的标识信息(例如第二承载的承载标识(bearer Id))、第二承载的无线接入类型以及第二承载对应的QoS文档。
第五记账会话的标识可以包括以下信息：第三计费标识、会话管理功能网元的地址以及第二承载的标识信息。第二承载的标识信息可以是指第二承载的承载标识或会话管理功 能网元分配的其他用于标识第二承载的信息。
步骤704：AAA服务器返回相应的响应消息。
可选的，会话管理功能网元决定在PDN连接中创建新的第三承载时，会话管理功能网元可以发起第三承载建立流程，具体过程不再赘述。在PDU会话中建立第三承载之后，可以建立第三承载对应的记账会话，具体包括以下步骤。
步骤705：会话管理功能网元向AAA服务器发送记账请求消息，用于请求开始对PDN连接中的第三承载进行记账。
该记账请求消息中携带的内容，本申请实施例并不限定，可以包括但不限于终端设备(或者称为用户)的标识、终端设备的地址、第三承载对应的第六记账会话的标识、第三计费标识、第三承载的标识信息、无线接入类型以及第三承载对应的QoS文档。
第六记账会话的标识可以包括以下信息：第三计费标识或第四计费标识、会话管理功能网元的地址以及第三承载的标识信息。第三承载的标识信息可以是指第三承载的承载标识或会话管理功能网元分配的其他用于标识第三承载的信息。第四计费标识为会话管理功能网元为第三承载分配的计费标识。
步骤706：AAA服务器返回相应的响应消息。
可选的，会话管理功能网元决定修改或删除第二承载时，会话管理功能网元可以向服务网关分别发送相应功能的消息，消息中携带第二承载的标识。例如，决定修改第二承载时，发送修改承载请求(modify bearer request)消息；决定删除第二承载时，发送删除承载请求(delete bearer request)，具体过程不再赘述。
进一步的，PDN连接建立完成之后，终端设备从第二网络切换到第一网络后，会话管理功能网元可以根据每个承载更新对应的记账会话，具体可以参考图7所示。如图7所示，为本申请实施例提供的一种通信方法流程示意图。
步骤801：会话管理功能网元确定将第二承载映射到在第一网络中所对应的第七QoS流，向AAA服务器发送记账请求消息。
需要说明的是，会话管理功能网元具体如何确定将第二承载映射到第七QoS流，本申请实施例对此并不限定。
其中，所述记账请求消息包括所述第五记账会话的标识和所述第七QoS流对应的信息，所述记账请求消息用于指示所述AAA服务器更新所述第五记账会话。第七QoS流对应的信息可以用于更新第五记账会话。
所述第七QoS流对应的信息包括以下一项或多项：
所述第七QoS流对应的无线接入类型；所述第七QoS流对应的分组过滤器；所述第七QoS流对应的QoS文档。
所述第七QoS流对应的信息还可以第三计费标识。
步骤802：AAA服务器返回相应的响应消息。
可选的，还可以包括以下步骤：
步骤803：会话管理功能网元确定将所述第三承载映射到在所述第一网络中所对应的第八QoS流，向AAA服务器发送记账请求消息。
其中，所述记账请求消息包括第六记账会话的标识和所述第八QoS流对应的信息，所述第八消息用于指示所述AAA服务器更新所述第六记账会话。
所述第八QoS流对应的信息包括以下一项或多项：
所述第八QoS流对应的无线接入类型；所述第八QoS流对应的分组过滤器；所述第八QoS流对应的QoS文档。
步骤804：AAA服务器对第六记账会话进行更新，并返回相应的响应消息。
如果在图7中，会话管理功能网元为第三承载分配了第四计费标识，则第八消息中还包括第三计费标识。
可选的，如果AAA服务器决定删除第七QoS流对应的资源，则可以向会话管理功能网元发送断开连接请求消息，断开连接请求消息中携带第五记账会话的标识。会话管理功能网元可以根据断开连接请求消息删除第七QoS流对应的资源，具体过程不再赘述。
需要说明的是，本申请实施例提供的各个实施例可以为独立的方案，也可以根据内在逻辑进行组合，这些方案都落入本申请的保护范围中。
上述本申请提供的实施例中，分别从各个设备之间交互的角度对本申请实施例提供的方法进行了介绍。为了实现上述本申请实施例提供的方法中的各功能，会话管理功能网元可以包括硬件结构和/或软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能以硬件结构、软件模块、还是硬件结构加软件模块的方式来执行，取决于技术方案的特定应用和设计约束条件。
本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。另外，在本申请各个实施例中的各功能模块可以集成在一个处理器中，也可以是单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
与上述构思相同，如图9所示，本申请实施例还提供一种装置900用于实现上述方法中会话管理功能网元的功能。例如，该装置可以为软件模块或者芯片系统。本申请实施例中，芯片系统可以由芯片构成，也可以包含芯片和其他分立器件。该装置900可以包括：处理单元901和通信单元902。
本申请实施例中，通信单元也可以称为收发单元，可以包括发送单元和/或接收单元，分别用于执行上文方法实施例中会话管理功能网元发送和接收的步骤。
以下，结合图9至图10详细说明本申请实施例提供的通信装置。应理解，装置实施例的描述与方法实施例的描述相互对应，因此，未详细描述的内容可以参见上文方法实施例，为了简洁，这里不再赘述。
通信单元902也可以称为收发器、收发机、收发装置等。处理单元901也可以称为处理器，处理单板，处理模块、处理装置等。可选的，可以将通信单元902中用于实现接收功能的器件视为接收单元，将通信单元902中用于实现发送功能的器件视为发送单元，即通信单元902包括接收单元和发送单元。通信单元902有时也可以称为收发机、收发器、或收发电路等。接收单元有时也可以称为接收机、接收器、或接收电路等。发送单元有时也可以称为发射机、发射器或者发射电路等。
处理单元，用于为终端设备在第一网络中建立协议数据单元会话，所述协议数据单元会话包括第一服务质量流；
通信单元，用于向认证授权记账服务器发送第一消息，所述第一消息包括所述第一服务质量流对应的第一记账会话的标识；
所述处理单元，用于确定所述终端设备从所述第一网络切换到第二网络后，将所述第 一服务质量流映射到在所述第二网络中所对应的第一承载；
所述通信单元，用于向所述认证授权记账服务器发送第二消息；
其中，所述第二消息包括所述第一服务质量流对应的第一记账会话的标识和所述第一承载的信息，所述第二消息用于指示所述认证授权记账服务器更新所述第一记账会话。
应理解，通信单元和处理单元还可以执行其他操作，例如通信单元902用于执行上述图4或图8或图10所示的方法实施例中会话管理功能网元的发送操作和接收操作，处理单元901用于执行上述图4或图8或图10所示的方法实施例中会话管理功能网元除了收发操作之外的其他操作，具体可以参考前面的描述，在此不再赘述。
如图10所示为本申请实施例提供的另一种通信装置，图10所示的装置可以为图9所示的装置的一种硬件电路的实现方式。该通信装置可适用于前面所示出的流程图中，执行上述方法实施例中会话管理功能网元的功能。为了便于说明，图10仅示出了该通信装置的主要部件。
装置1000还可以包括至少一个存储器1030，用于存储程序指令和/或数据。存储器1030和处理器1020耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接，可以是电性，机械或其它的形式，用于装置、单元或模块之间的信息交互。处理器1020可能和存储器1030协同操作。处理器1020可能执行存储器1030中存储的程序指令。所述至少一个存储器中的至少一个可以包括于处理器中。
图10所示的装置1000包括至少一个处理器1020以及通信接口1010，处理器1020用于执行存储器1030中存储的指令或程序。存储器1030中存储的指令或程序被执行时，该处理器1020用于执行上述实施例中处理单元901执行的操作，通信接口1010用于执行上述实施例中通信单元902执行的操作。
在本申请实施例中，通信接口可以是收发器、电路、总线、模块或其它类型的通信接口。在本申请实施例中，通信接口为收发器时，收发器可以包括独立的接收器、独立的发射器；也可以集成收发功能的收发器、或者是通信接口。
装置1000还可以包括通信线路1040。其中，通信接口1010、处理器1020以及存储器1030可以通过通信线路1040相互连接；通信线路1040可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。所述通信线路1040可以分为地址总线、数据总线、控制总线等。为便于表示，图10中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
本申请提还提供了一种计算机可读存储介质，用于存储计算机程序，该计算机程序包括用于执行上面任一流程中提供的方法的指令。
本申请提还提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上面任一流程中提供的方法。
本申请提还提供一种芯片，包括处理器，所述处理器与存储器耦合，用于执行所述存储器中存储的计算机程序或指令，当所述处理器执行所述计算机程序或指令时，使得上面任一流程中提供的方法被实现。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机 可用存储介质(包括但不限于磁盘存储器、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (29)

  1. 一种通信方法，其特征在于，包括：
    会话管理功能网元为终端设备在第一网络中建立协议数据单元会话，所述协议数据单元会话包括第一服务质量流；
    所述会话管理功能网元向认证授权记账服务器发送第一消息，所述第一消息包括所述第一服务质量流对应的第一记账会话的标识；
    所述会话管理功能网元确定所述终端设备从所述第一网络切换到第二网络后，将所述第一服务质量流映射到在所述第二网络中所对应的第一承载；
    所述会话管理功能网元向所述认证授权记账服务器发送第二消息；
    其中，所述第二消息包括所述第一服务质量流对应的第一记账会话的标识和所述第一承载的信息，所述第二消息用于指示所述认证授权记账服务器更新所述第一记账会话。
  2. 根据权利要求1所述的方法，其特征在于，所述协议数据单元会话还包括第二服务质量流；所述方法还包括：
    所述会话管理功能网元向所述认证授权记账服务器发送第三消息，所述第三消息包括所述第二服务质量流对应的第二记账会话的标识；
    所述会话管理功能网元将所述第二服务质量流映射到所述第一承载；
    所述会话管理功能网元向所述认证授权记账服务器发送第四消息，其中，所述第四消息包括所述第二服务质量流对应的第二记账会话的标识和所述第一承载的信息，所述第四消息用于指示所述认证授权记账服务器更新所述第二记账会话。
  3. 根据权利要求1至2任一所述的方法，其特征在于，所述会话管理功能网元向认证授权记账服务器发送第二消息之后，所述方法还包括：
    所述会话管理功能网元接收来自所述认证授权记账服务器的断开连接请求消息，所述断开连接请求消息包括所述第一记账会话的标识，所述断开连接请求消息用于请求删除所述第一服务质量流对应的资源；
    所述会话管理功能网元向服务网关发送更新承载请求，所述更新承载请求用于请求删除所述第一服务质量流对应的资源。
  4. 根据权利要求1所述的方法，其特征在于，所述协议数据单元会话还包括第三服务质量流；所述方法还包括：
    所述会话管理功能网元将所述终端设备的所述第三服务质量流映射到所述第一承载；
    所述会话管理功能网元向所述认证授权记账服务器发送第一停止指示信息和所述第三服务质量流对应的第三记账会话的标识，所述第一停止指示信息用于指示所述认证授权记账服务器停止所述第三记账会话。
  5. 根据权利要求1至4任一项所述的方法，其特征在于，所述协议数据单元会话还包括第四服务质量流，所述方法还包括：
    所述会话管理功能网元向所述认证授权记账服务器发送第五消息，所述第五消息包括所述第四服务质量流对应的第四记账会话的标识；
    所述会话管理功能网元确定所述终端设备从所述第一网络切换到所述第二网络后，确定所述第四服务质量流不映射到所述第二网络中的承载；
    所述会话管理功能网元向所述认证授权记账服务器发送第二停止指示信息和所述第 四服务质量流对应的第四记账会话的标识，所述第二停止指示信息用于指示所述认证授权记账服务器停止所述第四记账会话。
  6. 根据权利要求1至5任一所述的方法，其特征在于，所述第一记账会话的标识包括第一计费标识、所述会话管理功能网元的地址以及所述第一服务质量流的标识信息，所述第一计费标识是所述会话管理功能网元为所述协议数据单元会话分配的计费标识。
  7. 根据权利要求2至5任一所述的方法，其特征在于，所述第二记账会话的标识包括第一计费标识、所述会话管理功能网元的地址以及所述第二服务质量流的标识信息。
  8. 根据权利要求1至7任一所述的方法，其特征在于，所述第一承载的信息包括以下至少一项：
    所述第一承载对应的无线接入类型；所述第一承载对应的服务质量文档。
  9. 根据权利要求8所述的方法，其特征在于，所述第一承载的信息中还包括所述会话管理功能网元为所述第一承载分配的第二计费标识。
  10. 根据权利要求1至9任一所述的方法，其特征在于，所述方法还包括：
    所述会话管理功能网元确定所述终端设备从所述第二网络切换到所述第一网络后，将所述第一承载映射到在所述第一网络中所对应的第五服务质量流；
    所述会话管理功能网元向所述认证授权记账服务器发送第六消息；
    其中，所述第六消息包括所述第一记账会话的标识和所述第五服务质量流对应的信息，所述第六消息用于指示所述认证授权记账服务器更新所述第一记账会话。
  11. 根据权利要求10所述的方法，其特征在于，所述第五服务质量流对应的信息包括以下一项或多项：
    所述第五服务质量流对应的无线接入类型；所述第五服务质量流对应的服务质量文档。
  12. 根据权利要求10所述的方法，其特征在于，所述第五服务质量流对应的信息还包括所述第一计费标识。
  13. 根据权利要求10或11或12所述的方法，其特征在于，所述方法还包括：
    所述会话管理功能网元确定所述终端设备从所述第二网络切换到所述第一网络后，将所述第一承载映射到在所述第一网络中所对应的第六服务质量流；
    所述会话管理功能网元向所述认证授权记账服务器发送第七消息；
    其中，所述第七消息包括所述第二记账会话的标识和所述第六服务质量流对应的信息，所述第六消息用于指示所述认证授权记账服务器更新所述第二记账会话。
  14. 一种通信装置，其特征在于，包括：
    处理单元，用于为终端设备在第一网络中建立协议数据单元会话，所述协议数据单元会话包括第一服务质量流；
    通信单元，用于向认证授权记账服务器发送第一消息，所述第一消息包括所述第一服务质量流对应的第一记账会话的标识；
    所述处理单元，用于确定所述终端设备从所述第一网络切换到第二网络后，将所述第一服务质量流映射到在所述第二网络中所对应的第一承载；
    所述通信单元，用于向所述认证授权记账服务器发送第二消息；
    其中，所述第二消息包括所述第一服务质量流对应的第一记账会话的标识和所述第一承载的信息，所述第二消息用于指示所述认证授权记账服务器更新所述第一记账会话。
  15. 根据权利要求14所述的装置，其特征在于，所述协议数据单元会话还包括第二服务质量流；
    所述通信单元还用于：
    向所述认证授权记账服务器发送第三消息，所述第三消息包括所述第二服务质量流对应的第二记账会话的标识；
    所述处理单元还用于：将所述第二服务质量流映射到所述第一承载；
    所述通信单元还用于：向所述认证授权记账服务器发送第四消息，其中，所述第四消息包括所述第二服务质量流对应的第二记账会话的标识和所述第一承载的信息，所述第四消息用于指示所述认证授权记账服务器更新所述第二记账会话。
  16. 根据权利要求14至15任一所述的装置，其特征在于，所述通信单元还用于，在所述通信单元向认证授权记账服务器发送第二消息之后，
    接收来自所述认证授权记账服务器的断开连接请求消息，所述断开连接请求消息包括所述第一记账会话的标识，所述断开连接请求消息用于请求删除所述第一服务质量流对应的资源；
    向服务网关发送更新承载请求，所述更新承载请求用于请求删除所述第一服务质量流对应的资源。
  17. 根据权利要求14所述的装置，其特征在于，所述协议数据单元会话还包括第三服务质量流；所述处理单元还用于：
    将所述终端设备的所述第三服务质量流映射到所述第一承载；
    所述通信单元还用于，向所述认证授权记账服务器发送第一停止指示信息和所述第三服务质量流对应的第三记账会话的标识，所述第一停止指示信息用于指示所述认证授权记账服务器停止所述第三记账会话。
  18. 根据权利要求14至17任一项所述的装置，其特征在于，所述协议数据单元会话还包括第四服务质量流，所述通信单元还用于：
    向所述认证授权记账服务器发送第五消息，所述第五消息包括所述第四服务质量流对应的第四记账会话的标识；
    所述处理单元还用于：确定所述终端设备从所述第一网络切换到所述第二网络后，确定所述第四服务质量流不映射到所述第二网络中的承载；
    所述通信单元还用于向所述认证授权记账服务器发送第二停止指示信息和所述第四服务质量流对应的第四记账会话的标识，所述第二停止指示信息用于指示所述认证授权记账服务器停止所述第四记账会话。
  19. 根据权利要求14至18任一所述的装置，其特征在于，所述第一记账会话的标识包括第一计费标识、会话管理功能网元的地址以及所述第一服务质量流的标识信息，所述第一计费标识是会话管理功能网元为所述协议数据单元会话分配的计费标识。
  20. 根据权利要求14至18任一所述的装置，其特征在于，所述第二记账会话的标识包括第一计费标识、会话管理功能网元的地址以及所述第二服务质量流的标识信息。
  21. 根据权利要求14至20任一所述的装置，其特征在于，所述第一承载的信息包括以下至少一项：
    所述第一承载对应的无线接入类型；所述第一承载对应的服务质量文档。
  22. 根据权利要求21所述的装置，其特征在于，所述第一承载的信息中还包括会话 管理功能网元为所述第一承载分配的第二计费标识。
  23. 根据权利要求14至22任一所述的装置，其特征在于，所述处理单元还用于：
    确定所述终端设备从所述第二网络切换到所述第一网络后，将所述第一承载映射到在所述第一网络中所对应的第五服务质量流；
    所述通信单元还用于：向所述认证授权记账服务器发送第六消息；
    其中，所述第六消息包括所述第一记账会话的标识和所述第五服务质量流对应的信息，所述第六消息用于指示所述认证授权记账服务器更新所述第一记账会话。
  24. 根据权利要求23所述的装置，其特征在于，所述第五服务质量流对应的信息包括以下一项或多项：
    所述第五服务质量流对应的无线接入类型；所述第五服务质量流对应的服务质量文档。
  25. 根据权利要求23所述的装置，其特征在于，所述第五服务质量流对应的信息还包括所述第一计费标识。
  26. 根据权利要求23或24或25所述的装置，其特征在于，所述处理单元还用于：
    确定所述终端设备从所述第二网络切换到所述第一网络后，将所述第一承载映射到在所述第一网络中所对应的第六服务质量流；
    所述通信单元还用于：向所述认证授权记账服务器发送第七消息；
    其中，所述第七消息包括所述第二记账会话的标识和所述第六服务质量流对应的信息，所述第六消息用于指示所述认证授权记账服务器更新所述第二记账会话。
  27. 一种通信装置，其特征在于，包括：存储器与处理器，所述存储器用于存储指令，所述处理器用于执行所述存储器存储的指令，并且对所述存储器中存储的指令的执行使得，所述处理器用于执行如权利要求1至13中任一项所述的方法。
  28. 一种计算机可读存储介质，其特征在于，包括计算机可读指令，当通信装置读取并执行所述计算机可读指令时，使得所述通信装置执行如权利要求1至13中任一项所述的方法。
  29. 一种计算机程序产品，其特征在于，包括计算机可读指令，当通信装置读取并执行所述计算机可读指令，使得所述通信装置执行如权利要求1至13中任一项所述的方法。
PCT/CN2020/108743 2020-08-12 2020-08-12 一种通信方法及装置 WO2022032543A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP20949042.4A EP4191950A4 (en) 2020-08-12 2020-08-12 COMMUNICATION METHOD AND DEVICE
PCT/CN2020/108743 WO2022032543A1 (zh) 2020-08-12 2020-08-12 一种通信方法及装置
CN202080104172.7A CN116097622A (zh) 2020-08-12 2020-08-12 一种通信方法及装置
US18/167,460 US20230188957A1 (en) 2020-08-12 2023-02-10 Communication Method and Apparatus

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/108743 WO2022032543A1 (zh) 2020-08-12 2020-08-12 一种通信方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/167,460 Continuation US20230188957A1 (en) 2020-08-12 2023-02-10 Communication Method and Apparatus

Publications (1)

Publication Number Publication Date
WO2022032543A1 true WO2022032543A1 (zh) 2022-02-17

Family

ID=80246675

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/108743 WO2022032543A1 (zh) 2020-08-12 2020-08-12 一种通信方法及装置

Country Status (4)

Country Link
US (1) US20230188957A1 (zh)
EP (1) EP4191950A4 (zh)
CN (1) CN116097622A (zh)
WO (1) WO2022032543A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019158101A1 (en) * 2018-02-15 2019-08-22 Huawei Technologies Co., Ltd. Tracking qos violated events
CN110999344A (zh) * 2017-08-11 2020-04-10 三星电子株式会社 手动漫游和数据使用权
CN111052800A (zh) * 2018-08-10 2020-04-21 瑞典爱立信有限公司 用于促进互相配合网络中的pdu会话过程的方法和节点

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110999344A (zh) * 2017-08-11 2020-04-10 三星电子株式会社 手动漫游和数据使用权
WO2019158101A1 (en) * 2018-02-15 2019-08-22 Huawei Technologies Co., Ltd. Tracking qos violated events
CN111052800A (zh) * 2018-08-10 2020-04-21 瑞典爱立信有限公司 用于促进互相配合网络中的pdu会话过程的方法和节点

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CHINA TELECOM, HUAWEI: "Type of core network", 3GPP DRAFT; C3-194079-CORE NETWORK TYPE, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG3, no. Portoroz, Slovenia; 20191007 - 20191011, 30 September 2019 (2019-09-30), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051788266 *
ERICSSON: "Correct access challenge", 3GPP DRAFT; C3-202480, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. CT WG3, no. Online Meeting ;20200416 - 20200424, 25 April 2020 (2020-04-25), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051878457 *

Also Published As

Publication number Publication date
EP4191950A1 (en) 2023-06-07
CN116097622A (zh) 2023-05-09
US20230188957A1 (en) 2023-06-15
EP4191950A4 (en) 2023-08-30

Similar Documents

Publication Publication Date Title
US11917498B2 (en) Communication method and communications apparatus
CN111602452B (zh) 用于多播-广播会话释放和修改的方法和系统
EP3965440A1 (en) Sidelink communication method and apparatus, and storage medium
KR102272582B1 (ko) Qos 흐름 처리 방법 및 기기, 그리고 통신 시스템
US20220217587A1 (en) Session Handling Method and Related Device
JP2019530363A (ja) 通信のための方法、装置、システム、端末、およびアクセス・ネットワーク・デバイス
US20220201539A1 (en) Method for obtaining data radio bearer identifier and base station
US10945180B2 (en) Mobility management method, apparatus, and system
US20220322135A1 (en) Method for managing qos, relay terminal, pcf network element, smf network element, and remote terminal
CN105874830A (zh) 一种移动性管理的方法、装置及系统
CN107846703B (zh) 一种数据传输方法及装置
WO2020224412A1 (zh) 一种通信方法及装置
WO2018233451A1 (zh) 通信方法、装置和系统
CN110431866B (zh) 控制面连接管理方法和装置
EP2632093A1 (en) Packet switched domain service processing method and device
WO2024037611A1 (zh) 注册信息同步方法、装置、设备及介质
KR100773822B1 (ko) 효율적인 ＩＰｖ６용 ＩＰ 주소 할당을 위한 전화 접속네트워킹 방법
CN113573381A (zh) 非ip类型数据的传输处理方法、设备、装置及介质
WO2022032543A1 (zh) 一种通信方法及装置
CN111867146B (zh) 一种标识信息发送、接收方法、设备及装置
WO2021042381A1 (zh) 一种通信方法、装置及系统
WO2022089660A1 (zh) 切换方法、终端和网络侧设备
WO2022061916A1 (zh) 一种通信方法及装置
WO2022228006A1 (zh) 一种业务流识别方法及装置
CN117858068A (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: 20949042

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2020949042

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2020949042

Country of ref document: EP

Effective date: 20230227

NENP Non-entry into the national phase

Ref country code: DE